Tried this
setup / Alienx simple remaster CD
* Running the script gave me instructions so just followed those
* I installed 3 extra browsers to get a unique ISO
* Cleaned up unneeded files and set up a background, icon positions etc
* created a directory on my HD with rox by going to to /mnt/home (that is the HD) so I have a directory on my HD (where the pup001 and in this case pup004 are stored) called iso_remaster
* ran script (do not do anything else whilst running script) choose remaster fast
* selected HD location and followed script
* choose to NOT have it set up for my machines setup - so would be a distro
* waited about 2 minutes (there was an error message cp: cannot stat `/mnt/cdrom/goofy.16) BUT it created an ISO which I burnt
* It worked but the browser links on the desktop had error messages
Bit of tweaking and this is truly amazing . . .
your own distro . . .
with remaster I got an iso - took about 10 minutes - had to watch the HD for activity
The iso once burnt refused to boot up to xwindows and there was a lot of error messages during boot so the faster method worked better for me.
needs more testers . . .
and here is a spelling mistake (not that my spelling is any good) from the script:
TIP:
when we install a lot of dotpups, folder /root/my-applications becomes big and
then file image.gz also this is not good for low ram computers.
So I suggest that before renning script user moves /root/my-applications to
/usr and symlink it back to /root, file image.gz will be smaller.
107a: Setup / Alienx simple remaster CD
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Ah yes, 1.0.7alpha doesn't have a boot image -- that's what goofy.16 is.waited about 2 minutes (there was an error message cp: cannot stat `/mnt/cdrom/goofy.16) BUT it created an ISO which I burnt
I was experimenting with just a plain text boot menu
...nobody has commented on that!
...it could be jazzed up with colored text.
- Pizzasgood
- Posts: 6183
- Joined: Wed 04 May 2005, 20:28
- Location: Knoxville, TN, USA
Or ASCII art! Vector had a penguin made out of colored ASCII art.
I haven't had a chance to try the alpha, but I don't have a problem with text. I only look at the screen long enough to hit enter anyway.
I haven't had a chance to try the alpha, but I don't have a problem with text. I only look at the screen long enough to hit enter anyway.
[size=75]Between depriving a man of one hour from his life and depriving him of his life there exists only a difference of degree. --Muad'Dib[/size]
[img]http://www.browserloadofcoolness.com/sig.png[/img]
[img]http://www.browserloadofcoolness.com/sig.png[/img]
The lack of eye candy doesn't bother me, but only having a few seconds to figure out what the (new) text means does. I'm 56 years old but I read at a 59-year-old level. Seriously, the boot choices are a bit confusing to me. I'm no expert in computers or Puppy but I'm not a beginner either.BarryK wrote:...I was experimenting with just a plain text boot menu
...nobody has commented on that!
...it could be jazzed up with colored text.
Problem booting 1.0.7 alpha ISO on Thinkpad T30
1.0.6 boots with the puppy image (goofy.16 I guess) on my T30. The 1.0.7 alpha does not boot at all on the same T30. I burned several iso images on different machines (linux and XP), but no luck. The same disks do boot on a Fujitsu Scenic (selecting Xorg produces a beautifuly garbled colour screen...but that's for another post...)
Just to make things more complicated the 1.0.7 alpha disks failed to boot a similar fujitsu Scenic machine with a different DVD drive. Gave an error message after the initial menu selection option was entered. The actual selection didn't matter. Disk access error... (don't have it to hand now).
What is the logical explanation for the different booting behaviour of 1.0.7 alpha on different machines?
Or am I missing something obvious...
Just to make things more complicated the 1.0.7 alpha disks failed to boot a similar fujitsu Scenic machine with a different DVD drive. Gave an error message after the initial menu selection option was entered. The actual selection didn't matter. Disk access error... (don't have it to hand now).
What is the logical explanation for the different booting behaviour of 1.0.7 alpha on different machines?
Or am I missing something obvious...