Pizza & Bare Puppy not booting on HD with LinLd.

[sunburnt]

I'm setting up a bunch of Puppy vers. on a Fat32 HD to try them all out.
Useing LinLd it's easy while booting to press F8 to go to DOS, or to drop out of Win to DOS, & run the Puppys with batch files.

I copy the proper usr_cram.fs to C:\ before Puppy's run.

Puppy1.0.5 works great, near as I can tell all the apps. work.
It even works great LAN booting from Win98 useing tftpd32, I LOVE IT!
==================
"Puppy105.bat" file:
linld.com image=vmlinuz initrd=image.gz cl=@puppy.lin

"puppy.lin" file:
root=/dev/ram0
PFILE=pup001-none-262144
PHOME=hda6

Pizza1.0.5 barely boots & FireFox won't start (that's why I wanted it).
==================
"Pizza105.bat" file:
linld.com image=vmlinuz initrd=image.gz cl=@pizza.lin

"pizza.lin" file:
root=/dev/ram0
ramdisk_size=50603
PFILE=pup015-none-262144
PHOME=hda6
==================

BarePuppy won't boot at all, I know it's stripped, but I wanted to look at it.
Are my files wrong, or is this solved by putting usr_cram.fs in Image.gz?
If so, I assume that usr_cram.fs doesn't have to be put in side of the image file that's inside of Image.gz, just gzipped in with it.

[Pizzasgood]

You're probably already doing this, but better to ask than to be wrong: You are using the right image.gz files, right? They aren't interchangeable. Pizzapup needs the one that comes with it. Barebones needs the one it comes with.

Otherwise, the only thing I can think of is if size matters. Pizzapup's image.gz is a good bit (about 3X) bigger than the standard.

[sunburnt]

Strangely I deleted the pup015 file (I think I got that right) & it came up correctly.
Puppy 1.0.5 booted to a black screen after some messing around & I had to do the same thing to fix it.

Does this happen very much for Puppy & its variants?

[MU]

On my system that doesn't happen.

I copied the files as described, but I don't use the Grub from Puppy, but WinGrub on my XP-Partition.

But different hardware - different behaviour.
You talked about 128 MB-Harddisk.
It will be quite old, so there might be defect sectors on it?

You could try to run e2fsck to check the Puppy-Filesystem. But this will not check the entire harddisk, I don't know how to do that with puppy.

Mark

[Guest]

Excuse my newbieness folks.
i did manage to run barbones puppy using tiny,why did it work but not linld or loadlin i have no idea.
vmlinuz (in C:\)
image.gz (in C:\)
usr_cram.fs (in C:\)

Sorry for posting off topic but can you please guys help me with a problem..plz

i downloaded the ltmodem packages (all three) using windows then i installed the first and it should of shown the ttylt0 button after rebooting but didn't the uninstalled the package ->rebooted and installed another with no luck and same with the last lt package but didn't work either.....please note that i have puppy 1.6 installed on /dev/hda6 and when i installed the ltmodem package it worked just fine?!
can you please help me with as i need to install barebones on a 128mb flashdrive and bare bones saves me much needed space on that flash drive.
Thanks

[sunburnt]

Guest; you'd have to post your: xxxx.lin file that linld.com uses, loadlin is somewhat defective but usable, linld is better & I suspect tiny might be even better.