Mike Walsh
Fri Mar 13, 2015 4:46:21 pm
Afternoon, everybody; back after a break of about 6 or 7 months.
Using Zorin Core OS 9. I had removed it a while back (I was still 'distro-hopping' at that stage), but I've since settled down with Ubuntu 14.04 LTS, which has been there since I first moved to Linux last May.....and Puppy Linux.
I decided to re-install Zorin a few nights ago. Initially, I was trying to install it to a flash drive (a FULL install), but it just didn't want to know. I've done a couple of 'buntu-based flash installs over the last few months, with varying degrees of success.....but they DO seem to run awfully slowly, so.....I don't know. Has anybody else managed a flash drive install.....and if so, how did you do it?
I've re-installed Zorin on my external Seagate Expansion drive. It's booted up every time, until today, when I had a wee bit of trouble getting it to start. Because I run Puppy, I don't run GRUB2; it refuses to 'see' Puppy, so consequently I can't boot it. I run Grub4DOS instead, which is supplied with Puppy; it always works, and reads every OS that's installed. GRUB2 probably doesn't 'see' Puppy because of the way Puppy is set up.....which is a compressed, 'frugal' install from an .sfs file; it expands into RAM at bootup, and resides there, IN RAM, for the duration of the session. Which accounts for Puppy's incredible speed!
With Grub4DOS, you get to see all the start-up stuff that GRUB2 hides from you. Attempting to boot a little while ago, it took 3 attempts to get things going. The first two times, I kept getting the message, 'Attention! /dev/sdb5 does not exist!' (/dev/sdb5 is the Seagate partition Zorin is installed to). Couldn't figure out what was going on, until I realised the only difference was that I was booting up with the printer switched on ( I normally turn it on after boot). Turned it off, booted again, and this time, everything proceeded as normal. Odd, no?
Anybody got the remotest idea what might have caused this to happen? For instance, if Zorin had been configured with the printer switched ON, would it always EXPECT the printer to be on AT boot-up?
I'm just curious, that's all!
Regards,
Mike.
Using Zorin Core OS 9. I had removed it a while back (I was still 'distro-hopping' at that stage), but I've since settled down with Ubuntu 14.04 LTS, which has been there since I first moved to Linux last May.....and Puppy Linux.
I decided to re-install Zorin a few nights ago. Initially, I was trying to install it to a flash drive (a FULL install), but it just didn't want to know. I've done a couple of 'buntu-based flash installs over the last few months, with varying degrees of success.....but they DO seem to run awfully slowly, so.....I don't know. Has anybody else managed a flash drive install.....and if so, how did you do it?
I've re-installed Zorin on my external Seagate Expansion drive. It's booted up every time, until today, when I had a wee bit of trouble getting it to start. Because I run Puppy, I don't run GRUB2; it refuses to 'see' Puppy, so consequently I can't boot it. I run Grub4DOS instead, which is supplied with Puppy; it always works, and reads every OS that's installed. GRUB2 probably doesn't 'see' Puppy because of the way Puppy is set up.....which is a compressed, 'frugal' install from an .sfs file; it expands into RAM at bootup, and resides there, IN RAM, for the duration of the session. Which accounts for Puppy's incredible speed!
With Grub4DOS, you get to see all the start-up stuff that GRUB2 hides from you. Attempting to boot a little while ago, it took 3 attempts to get things going. The first two times, I kept getting the message, 'Attention! /dev/sdb5 does not exist!' (/dev/sdb5 is the Seagate partition Zorin is installed to). Couldn't figure out what was going on, until I realised the only difference was that I was booting up with the printer switched on ( I normally turn it on after boot). Turned it off, booted again, and this time, everything proceeded as normal. Odd, no?
Anybody got the remotest idea what might have caused this to happen? For instance, if Zorin had been configured with the printer switched ON, would it always EXPECT the printer to be on AT boot-up?
I'm just curious, that's all!
Regards,
Mike.