.

Booting, installing, newbie
Post Reply
Message
Author
brianez21

.

#1 Post by brianez21 »

.
Last edited by brianez21 on Fri 14 Jun 2013, 22:56, edited 3 times in total.

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#2 Post by rcrsn51 »

First check that the file pupxxx.sfs is actually on the device. Then try changing syslinux.cfg to PMEDIA=idehd.

brianez21

#3 Post by brianez21 »

.
Last edited by brianez21 on Fri 14 Jun 2013, 23:00, edited 1 time in total.

brianez21

#4 Post by brianez21 »

.
Last edited by brianez21 on Fri 14 Jun 2013, 22:59, edited 1 time in total.

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#5 Post by rcrsn51 »

Congratulations. I suspect that the problem was not with Puppy but with syslinux. According to its documentation, syslinux won't work with a FAT32 drive. However a different boot loader like GRUB would launch Puppy fine.

brianez21

#6 Post by brianez21 »

.
Last edited by brianez21 on Fri 14 Jun 2013, 22:59, edited 1 time in total.

Bruce B

#7 Post by Bruce B »

brianez21 wrote:Okay here's what was wrong.

{cut}

Then I ran mkfs.msdos /dev/hda1 (do not use vfat, Puppy doesn't like FAT32 for some reason) and reinstalled through the Universal Installer.
I don't know how you arrived at that conclusion. Puppy's scripts looks for FAT32 partitions and uses them. It has for a long time.

brianez21

#8 Post by brianez21 »

.

Post Reply