It is my understanding that what mkswap does is "format" the blank new Linux partition, sort of, in other words it puts the special ext2 swap filesystem on the type-82 partition. mkswap needs to be run only once.
I repartitioned my harddisk, changed the swap partition to 192Mb. I still can't boot 1.08 but I can boot 1.06. Success! Kinda ....
Because I was using grub to dual boot DSL and Win98 and I forgot to "fdisk /mbr" to remove the dual boot from my hard disk before trashing the DSL partition. No problem if I could boot from a floppy but ... no floppy drive. No usb-ports either. Gonna have to dig up a bootable cd -- bootable into dos that is. I've found instructions for resetting the MBR from Linux but that sounds pretty risky. Have to see tomorrow,
I've never touched my mbr. So, I don't have experience with what you're talking about.
I run grub from autoexec.bat when I choose a "Puppy" option, displayed by my Win98SE c:\config.sys.
Whether to boot Win98SE or Puppy is chosen from just menu options when Windows boots (or, I should say, attempts to boot, until I choose the Puppy menu option, thereby deflecting the Microsoft borg from its intended course); the option of whether to boot to Puppy is displayed by Windows' own config.sys.
I understand that grub.exe can also be loaded as a device= option by config.sys but I have not tried this. Grub.exe runs as an executable under DOS provided you have your high memory managed (dos=,device=himem.sys,device=emm386,device=ifshlp.sys) as given in my post to pelokwin, above.
Perhaps I am having an easy time of using grub because I am storing Puppy only on FAT16 (USB flash key) or FAT32 (same hard disk partition as Windows 98SE) partitions. I have no experience in trying to start Puppy residing on an ext2 or ext3 partition using grub, so do not know in what particulars it differs.
So my own "dual boot" (quintuple boot, actually, I'm experimenting with four varieties of Puppy) doesn't depend on any special boot-time partition management software and I don't use (at least, I don't think I do) grldr.
Puppy 1.0.8 defaults to a 256MB pup100 or pup001 file, whereas earlier versions used only 128MB. However toddyjoe reports it runs fine on his computer with only 64MB of RAM and no swap. If the sum of your RAM plus your swap partition is under 256MB, maybe 1.0.8 will take a long time to load.
What trouble is 1.0.8 giving you?
Last edited by Sit Heel Speak on Tue 18 Apr 2006, 23:36, edited 1 time in total.
ckx, I cannot really offer you any help with the partition. Like Sit Heel Speak, I am doing my dual-booting (Win 98 SE and Puppy 1.0.8r1) off of one hard drive with GRUB and a few mods to the "config.sys" and "Autoexec.bat" files. My 1.6Gb hard drive has a single FAT32 partition for Windows and Puppy with no extra partitioning. The hard drive for my 310ED originally was FAT16 with Windows 95 but I converted to FAT32 using the program within Windows when I made the conversion to Windows 98 SE.
pelokwin, I think Sit Heel Speak has the right idea here with essentially restarting with a clean slate. Like you, I am kind of getting lost with the questions, answers and information being exchanged (but it must feel good to know you have a good resource for lots of help here!). Rather than me offering interrupting comments that might be at odds with other posters, I am going to watch how this new exchange between you and Sit Heel Speak pans out and only comment if I see something glaringly problematic. Maybe we can all get to the bottom of this that way and create a much less confusing thread.
toddyjoe wrote:pelokwin, I think Sit Heel Speak has the right idea here with essentially restarting with a clean slate.
But let's try doing it the gentle way first, leaving the existing partition intact. I know that you already have grub.exe *somewhere*, either on floppy or on the LiveCD or on disk. All you have to do is get the basic Puppy files vmlinuz, image.gz, usr_cram.fs, pupxide, and isolinux.cfg onto the C:\ directory of your hard disk. Once you accomplish that, then it is simply a matter of figuring out what to put in grub.exe's menu.lst config file, and it will be easy to set you up to boot in the identical manner as toddyjoe and I do.
PS if you are at a C:\WINDOWS> prompt, simply type
Sit heel speak:
Ok I have a folder in the C: named Puppy in that I have : image--- GZ file
isolinux.bin---bin file
usr_cram.fs---fs file
vmliuz--------file and a folder named bootgrub with:
grub
Menu.lst
Now first off I never saw pupxide , the only things left on the iso are BOOT.CAT and boot.msg
the way I feel is I should go step by step....so what is the next one and what do I do about pupxide?
Pelokwin
Ah--silly me. I forgot--you have a CD-ROM reader permanently installed on your Thinkpad. Windows/DOS is seeing the CD-ROM as drive D:. Your compressed drive must be Drive E:.
same error as before "it is not a compressed drive"
I looked at the properties for drive h and it said"host for c H is the host drive for the compressed drive C
and tell me if you see a line in the top, "Modules using memory below 1 MB:" part, which says DRVSPACE and six numbers.
Oh. I just realized (sorry, it's been a loooooong time since I dealt with DriveSpace; 1998, to be exact): it might be that it wants the letter of the _compressed_ drive, not the letter it maps it to.
Question
"When tasks is complete your computer will no longer contain any compressed drives. Do you want to remove the compression driver from memory at that time?"
I think the "call it a night" is a good idea I am going to let the comp do it's thing and will go to the next step tomorow. so I will talk to you later
thank you for all your help
Pelokwin