Linux in Windows Office environment

I dont understand the advice in here, there is a software compatibility issue and people are giving advice on networking? Why am I so lost in these replies?
Where do you get that from?
 
Hi guys

hoping someone have maybe some advise here.

I am finally getting tired of the resource hog windows 10 is (after the latest update performance just went from bad to worse - looking at almost 8 minutes just to boot.)

since i use my work laptop most of the time, this is the first machine i would like to convert. Problem is, that we work on a client /server setup in the office (eg all documents / spreadsheets is saved on a central windows share).

I attempted this migration about a year ago using ubuntu + openoffice, but had issues with some excel documents where it corrupts after opening it on the linux machine ( eg windows machine saves document, linux is able to open/edit and save it, but after that the windows machine cant read it anymore)

it will be a major PITA for me to run windows in a VM to test all documents first, but i really cant risk corrupting company files(some of these is spreasheets that is backup data for company proposals)

has anyone else recently migrated in a similar scenario and maybe have some advice for me?


TIA

Yeah, Windows 10 Pro, SSD = 7 second boot up
 
I would say replace your HDD, the only time my Windows 10 took long to boot was right before the HD crashed.
 
Hi guys

hoping someone have maybe some advise here.

I am finally getting tired of the resource hog windows 10 is (after the latest update performance just went from bad to worse - looking at almost 8 minutes just to boot.)

since i use my work laptop most of the time, this is the first machine i would like to convert. Problem is, that we work on a client /server setup in the office (eg all documents / spreadsheets is saved on a central windows share).

I attempted this migration about a year ago using ubuntu + openoffice, but had issues with some excel documents where it corrupts after opening it on the linux machine ( eg windows machine saves document, linux is able to open/edit and save it, but after that the windows machine cant read it anymore)

it will be a major PITA for me to run windows in a VM to test all documents first, but i really cant risk corrupting company files(some of these is spreasheets that is backup data for company proposals)

has anyone else recently migrated in a similar scenario and maybe have some advice for me?


TIA
Openoffice is dead since circa 2011 already. It got forked and renamed to LibreOffice and everyone and every distro moved on to that. It's available on Windows aswell so download it > make a backup of that Excel files > test it with LibreOffice > open with Excel. If it works then proceed to install Ubuntu or any other distro.
 
yikes - i missed quite a few replies already :o

Yes i noticed the libreoffice change, and did take the plunge over the weekend - Dual booting Mint with libre office. Will test it a few times saving a new copy to see if any issues arises again.

Office 365 seem to be the general solution though as far as i have seen , but dont think the company is ready to upgrade to it yet.


as for the slow boot - it only started after the most recent windows update. i am tempted to try a clean install, but having done that 50 times to many over the last 15 years, i am really starting to loose my faith in windows.
I agree that the laptop hard drive could be to blame (fragmented probably), but its not giving any bad sector warnings or corrupting any files as such. an SSD upgrade will be a dream - having done that for my home pc recently (and added 8GB of RAM), the 6 year old machine is flying with windows 10. Problem once gain is to get management to give out the $$$'s for the upgrade - not going to upgrade it out of my own pocket.


Must admit - getting everything working on Mint as i am used to on windows 10 is going to be a challenge - as long as it doesn't influence my productivity for too long. At least the Ubuntu/Mint community is quite strong.

The one thing that stumped me yesterday is that wpad support (Auto proxy) doesnt seem to be well supported. I ended up configuring the proxy manually. Will give me some pains when i travel/connect to other networks, but 99% of the time it should work

@Thor JEALOUS!!!! (no i am not on a network domain - boot time is measured until windows stopped accessing the HDD. only bootup applications i have according to the taskbar is Dropbox and skype :/)
 
1 - 3 seconds is life.

Haha. After I built the PC I had issues with random freezes & blue screens. But when a reboot takes 3 seconds I couldn't give a flying **** about tracing what the problem was :D Luckily after a few months of BIOS upgrades the problem seems to have gone away.

What drive do you have?
 
Haha. After I built the PC I had issues with random freezes & blue screens. But when a reboot takes 3 seconds I couldn't give a flying **** about tracing what the problem was :D Luckily after a few months of BIOS upgrades the problem seems to have gone away.

What drive do you have?
Exact same. Drive.


I had similar issues was down to something in the bois that had to be checked if you use m.2

Also the laptop had a Nvidia card, but Adobe defaults to the onbaord card so Adobe crashed my machine blue screen each time I tried to open it.


Changed preferences to use Nvidia at all costs.
 
Exact same. Drive.
I had similar issues was down to something in the bois that had to be checked if you use m.2
Also the laptop had a Nvidia card, but Adobe defaults to the onbaord card so Adobe crashed my machine blue screen each time I tried to open it. Changed preferences to use Nvidia at all costs.

Ah. It's a nice drive! Mine runs hot though. 51' yesterday when idle... damn durban weather.

My freezes were mostly avoided by disabling the cpu c-states, but were later fixed with a cpu microcode update.
 
Windows 10, resource hog? :erm: It's the snappiest OS I've seen on a PC specced for Windows Vista ;)
 
Brand new PC i5 6500, 8GB RAm 2133Mhz, HDD drive.

brand new windows 10 install - boot time (to login screen 30 secs - , another 40 secs after password input - cant click anything in this period)

Linux Mint Cinnamon 17 - 20 secs , usable immediately when desktop is shown, Firefox opens immediately.

Windows is a resource HOG.Hate it !!!
 
Brand new PC i5 6500, 8GB RAm 2133Mhz, HDD drive.

brand new windows 10 install - boot time (to login screen 30 secs - , another 40 secs after password input - cant click anything in this period)

Linux Mint Cinnamon 17 - 20 secs , usable immediately when desktop is shown, Firefox opens immediately.

Windows is a resource HOG.Hate it !!!

And yet my standard hdd equipped i3 loads the password screen in around 5 seconds and is ready to go on the desktop in less than 20...

PEBKAC issue perhaps? ;)
 
And yet my standard hdd equipped i3 loads the password screen in around 5 seconds and is ready to go on the desktop in less than 20...

PEBKAC issue perhaps? ;)

I am using a 7 year old HDD,maybe that is why.

No, its more like a PICNIC error :-P
 
Top
Sign up to the MyBroadband newsletter
X