WakePup2 v0.2 - Floppy boot disk (or boot CD) for Puppy2
- Sit Heel Speak
- Posts: 2595
- Joined: Fri 31 Mar 2006, 03:22
- Location: downwind
Welcome to the kennels,
If you are working in Windows: rawrite is not a Microsoft utility, it's 3rd-party, so you must go get it.
You can go here:
http://www.chrysocome.net/rawwrite
and download rawwritewin-0.7.zip, unzip it, and then run winrawwrite (or whatever they call it).
If your machine is capable of booting a Puppy live-CD, you can click
Menu -> Setup -> Wakepup create boot floppy
and create the Wakepup boot floppy from within Puppy.
A freedos version (rawrite3.com) is here, don't know whether it will work in a cmd window in newer Windows or not:
http://www.fdos.org/ripcord/rawrite/
Other versions can be found, use Google or the equivalent.
HTH, SHS
If you are working in Windows: rawrite is not a Microsoft utility, it's 3rd-party, so you must go get it.
You can go here:
http://www.chrysocome.net/rawwrite
and download rawwritewin-0.7.zip, unzip it, and then run winrawwrite (or whatever they call it).
If your machine is capable of booting a Puppy live-CD, you can click
Menu -> Setup -> Wakepup create boot floppy
and create the Wakepup boot floppy from within Puppy.
A freedos version (rawrite3.com) is here, don't know whether it will work in a cmd window in newer Windows or not:
http://www.fdos.org/ripcord/rawrite/
Other versions can be found, use Google or the equivalent.
HTH, SHS
WakePup2 - Floppy Boot disk
Thanks very much - I'll download the 'rawrite' file and try again.
-
- Posts: 6
- Joined: Sun 29 Nov 2009, 04:59
-
- Posts: 116
- Joined: Mon 07 Dec 2009, 04:30
Floppybootdisk asking for path or command at 'a' prompt
Hello,
I have been unable to boot my USB Flash Drive using the floppy boot disk.
The disk was made using WakePup create boot floppy in 4.31.
The Flash copy was made using BootFlash in 4.31.
The 1GB USB Flash D was formatted using GParted in 4.31. GParted is instructed to make VFAT16 and complies, but scans back afterward VFAT32. 'boot' flag was chosen.
Note: CFDISK scans the format as VFAT16.
Depending upon when I insert the USB Flash D, I get differing screen options/messages.
If USB Flash D inserted prior to power on, it is not found. The process then hangs.
If USB Flash D is not inserted at power on, menu comes up asking for media type.
Eventually, an 'a' prompt arrives. I do not know how to designate path, nor do I know what commands are possible/appropriate.
Please advise.
Mitchellray
I have been unable to boot my USB Flash Drive using the floppy boot disk.
The disk was made using WakePup create boot floppy in 4.31.
The Flash copy was made using BootFlash in 4.31.
The 1GB USB Flash D was formatted using GParted in 4.31. GParted is instructed to make VFAT16 and complies, but scans back afterward VFAT32. 'boot' flag was chosen.
Note: CFDISK scans the format as VFAT16.
Depending upon when I insert the USB Flash D, I get differing screen options/messages.
If USB Flash D inserted prior to power on, it is not found. The process then hangs.
If USB Flash D is not inserted at power on, menu comes up asking for media type.
Eventually, an 'a' prompt arrives. I do not know how to designate path, nor do I know what commands are possible/appropriate.
Please advise.
Mitchellray
Re: Floppybootdisk asking for path or command at 'a' prompt
Yes; gparted in 4.3.1 calls fat 16 partitions fat 32; it's weird.Mitchellray wrote:Hello,
I have been unable to boot my USB Flash Drive using the floppy boot disk.
The disk was made using WakePup create boot floppy in 4.31.
The Flash copy was made using BootFlash in 4.31.
The 1GB USB Flash D was formatted using GParted in 4.31. GParted is instructed to make VFAT16 and complies, but scans back afterward VFAT32. 'boot' flag was chosen.
Note: CFDISK scans the format as VFAT16.
Depending upon when I insert the USB Flash D, I get differing screen options/messages.
If USB Flash D inserted prior to power on, it is not found. The process then hangs.
If USB Flash D is not inserted at power on, menu comes up asking for media type.
Eventually, an 'a' prompt arrives. I do not know how to designate path, nor do I know what commands are possible/appropriate.
Please advise.
Mitchellray
A wakekpup2 floppy will not boot usbflash with puppy 4.3.1.
The floppy works fine on puppies earlier than 4.3.
The 4.3.1 flash can boot using the install cd and typing (puppy
pmedia=usbflash) at the boot screen.
Think I'll install 4.3.1 to flash again and check to see if it has the same
files as the earlier ones, (I should have done that before...duhh).
I used "universal installer" to "do the flash".
Inspiron 700m, Pent.M 1.6Ghz, 1Gb ram.
Msi Wind U100, N270 1.6>2.0Ghz, 1.5Gb ram.
Eeepc 8g 701, 900Mhz, 1Gb ram.
Full installs
Okay; tried it again....it works.
Wakepup2 gives you lots of stuff to read and think about.
Don't read.
Don't think.
Just hit enter.....eventually you have to click a number;
click number 1.
Wakepup2 gives you lots of stuff to read and think about.
Don't read.
Don't think.
Just hit enter.....eventually you have to click a number;
click number 1.
Inspiron 700m, Pent.M 1.6Ghz, 1Gb ram.
Msi Wind U100, N270 1.6>2.0Ghz, 1.5Gb ram.
Eeepc 8g 701, 900Mhz, 1Gb ram.
Full installs
-
- Posts: 116
- Joined: Mon 07 Dec 2009, 04:30
WakePup2 hangs
Hello rjbrewer,
When I insert the USB Flash D before powerup, WakePup2 proceeds to load but then hangs at a blinkin cursor.
On that page, it says it found USBFLASH, but a few lines down it says some type of adapter or converter (I'm not exactly certain) is not there.
Alternatively:
If I do not put USB Flash D in at powerup, WakePup2 gets to a screen asking for type of drive. I have tried both choices 1 and alternatively 6, both USB Flash Drive indicated.
Then the next step takes me to the choices 1 or 2, and I choose. Choice 1 results in a request for sub directory which must include USBFLASH.
I can not come up with the correct path.
Choice 2 results in a screen with a bit more detailed request for information and an a:\>.
I have no idea after trial and error what to place as path.
The only commands that seem to work are '?' and 'dir', but both get me to other screens where I am still at a loss.
Note: I have successfully booted my other computer, Asus1005HA with that USB Flash D after changing the bios to boot from peripheral 1st.
So the Flash Puppy is functional.
Mitchellray
When I insert the USB Flash D before powerup, WakePup2 proceeds to load but then hangs at a blinkin cursor.
On that page, it says it found USBFLASH, but a few lines down it says some type of adapter or converter (I'm not exactly certain) is not there.
Alternatively:
If I do not put USB Flash D in at powerup, WakePup2 gets to a screen asking for type of drive. I have tried both choices 1 and alternatively 6, both USB Flash Drive indicated.
Then the next step takes me to the choices 1 or 2, and I choose. Choice 1 results in a request for sub directory which must include USBFLASH.
I can not come up with the correct path.
Choice 2 results in a screen with a bit more detailed request for information and an a:\>.
I have no idea after trial and error what to place as path.
The only commands that seem to work are '?' and 'dir', but both get me to other screens where I am still at a loss.
Note: I have successfully booted my other computer, Asus1005HA with that USB Flash D after changing the bios to boot from peripheral 1st.
So the Flash Puppy is functional.
Mitchellray
Michellray;
I used "universal installer" to put puppy on the flash drive.
"Bootflash" gives me the impression it is for computers that
are new enough to boot usb without the need for floppy
I used "universal installer" to put puppy on the flash drive.
"Bootflash" gives me the impression it is for computers that
are new enough to boot usb without the need for floppy
Inspiron 700m, Pent.M 1.6Ghz, 1Gb ram.
Msi Wind U100, N270 1.6>2.0Ghz, 1.5Gb ram.
Eeepc 8g 701, 900Mhz, 1Gb ram.
Full installs
-
- Posts: 116
- Joined: Mon 07 Dec 2009, 04:30
WakePup2 cont'd
Hello,
I used universal installer to create the flash D files.
Does one of my results make it appear as if I used the BootFlash?
Mitchellray
I used universal installer to create the flash D files.
Does one of my results make it appear as if I used the BootFlash?
Mitchellray
Re: WakePup2 cont'd
From your initial post ;Mitchellray wrote:Hello,
I used universal installer to create the flash D files.
Does one of my results make it appear as if I used the BootFlash?
Mitchellray
"The Flash copy was made using BootFlash in 4.31. "
I hit 'enter' twice and 'number 1' once, to make it work.
Inspiron 700m, Pent.M 1.6Ghz, 1Gb ram.
Msi Wind U100, N270 1.6>2.0Ghz, 1.5Gb ram.
Eeepc 8g 701, 900Mhz, 1Gb ram.
Full installs
-
- Posts: 116
- Joined: Mon 07 Dec 2009, 04:30
WakePup2 cont'd
Hello,
Yes, I miswrote.
I used universal installer to create the flash D copy of 4.3.1.
Mitchellray
Yes, I miswrote.
I used universal installer to create the flash D copy of 4.3.1.
Mitchellray
Install 4.12 or 4.2 to flash and try it.
If it works, that eliminates wakepup from the equation,
(theoretically)
Edit: dec.16
Tried it with Barrys' latest experiment "Quirky-001"'
2.6.31.5 kernel and gparted makes 256 inode partitions,
same as 4.3.1.
Works fine
If it works, that eliminates wakepup from the equation,
(theoretically)
Edit: dec.16
Tried it with Barrys' latest experiment "Quirky-001"'
2.6.31.5 kernel and gparted makes 256 inode partitions,
same as 4.3.1.
Works fine
Inspiron 700m, Pent.M 1.6Ghz, 1Gb ram.
Msi Wind U100, N270 1.6>2.0Ghz, 1.5Gb ram.
Eeepc 8g 701, 900Mhz, 1Gb ram.
Full installs
-
- Posts: 116
- Joined: Mon 07 Dec 2009, 04:30
WakePup2 cont'd
Hello rjbrewer,
Yes, I had success with 4.2.1.
Oddly, WakePup2 only finds two of my USB, the ones on the motherboard, but not the additional two plugged into the auxiliary USB plug on the board.
Thanks much for the assistance.
Mitchellray
sidenote: Puppy would not shut off machine from FDD boot of USBFlash as was solved elsewhere with CD-RW by apm power_off=1.
But boot option acpi=force and then save on shutdown works on subsequent boots.
Yes, I had success with 4.2.1.
Oddly, WakePup2 only finds two of my USB, the ones on the motherboard, but not the additional two plugged into the auxiliary USB plug on the board.
Thanks much for the assistance.
Mitchellray
sidenote: Puppy would not shut off machine from FDD boot of USBFlash as was solved elsewhere with CD-RW by apm power_off=1.
But boot option acpi=force and then save on shutdown works on subsequent boots.
SOLVED wakepup2 problem: "lupu-501.sfs not found"
wakepup2 is a great tool for old computers!
PROBLEM:
I boot from floppy with wakepup2, but every time failed after a short boot, with the message:
Loading drivers needed to access disk drives.... done
Searching for Puppy files in computer disk drives...lupu-501.sfs not found. Drop ping out to initial-ramdisk console....
/bin/sh: can't access tty; job control turned off
#
SOLUTION:
After many tests I get the point: wakepup2 is case sensitive! It is looking for lupu-501.sfs, but in install folder the file is LUPU_501.SFS. For this reason is coming the message above. I solved that by renaming LUPU_501.SFS in lupu-501.sfs. Everything is working fine.
SUGGESTION:
Please edit wakepup2 to look for LUPU_501.SFS instead of lupu-501.sfs. Thank you!
PROBLEM:
I boot from floppy with wakepup2, but every time failed after a short boot, with the message:
Loading drivers needed to access disk drives.... done
Searching for Puppy files in computer disk drives...lupu-501.sfs not found. Drop ping out to initial-ramdisk console....
/bin/sh: can't access tty; job control turned off
#
SOLUTION:
After many tests I get the point: wakepup2 is case sensitive! It is looking for lupu-501.sfs, but in install folder the file is LUPU_501.SFS. For this reason is coming the message above. I solved that by renaming LUPU_501.SFS in lupu-501.sfs. Everything is working fine.
SUGGESTION:
Please edit wakepup2 to look for LUPU_501.SFS instead of lupu-501.sfs. Thank you!
pakt wrote:
Must change some of this to lower case, or it won't work.
(at least not with later versions of Puppy Linux)
Edit: clarification below
So instead, try doing it this way:
2) In Linux, copy WKPUP202.ZIP to a temp dir and execute:
# unzip WKPUP202.ZIP
# dd if=WKPUP202.IMG of=/dev/fd0 bs=1440k
Must change some of this to lower case, or it won't work.
(at least not with later versions of Puppy Linux)
Edit: clarification below
So instead, try doing it this way:
In Linux, copy wkpup202.zip to a temp directory
(Menu / Filesystem / ROX-Filer file manager, then green "up" arrow / tmp)
Right-click inside /tmp/ directory window, then left-click "Window"
Left-click "Terminal Here"
Type in the following EXACTLY AS SHOWN:
# unzip wkpup202.zip
# dd if=WKPUP202.IMG of=/dev/fd0 bs=1440k
Last edited by Dewbie on Sun 08 Jan 2012, 22:44, edited 2 times in total.
This is for WakePup2 v0.2.
(page 1, first post, this thread)
It has only the acpi boot-options menu.
I have attached a pfix options menu, including filesystem check.
Just replace the AUTOEXEC.BAT file with this one.
(page 1, first post, this thread)
It has only the acpi boot-options menu.
I have attached a pfix options menu, including filesystem check.
Just replace the AUTOEXEC.BAT file with this one.
- Attachments
-
- autoexecbat_pfix.tar.gz
- (1.75 KiB) Downloaded 686 times
I can boot Puppy 4.2.1 from an USB stick through a floppy diskette quite well, but I can not boot Puppy 4.3.1 and 5.1.1. I do not understand this suggestion about lower case. How to edit wakepup2 to look for lower case since the file is in lower case anyway, or how to replace the AUTOEXEC.BAT? Or maybe there is a later Puppy without these problems?
I've never used WakePup2 with USB, but for me it works fine with 2.14x / 4.1.2 / 4.3.1 / 5.1.1 / 5.1.4.1 when booting from floppy to IDE marker file (which is copied from floppy to hard drive).I can boot Puppy 4.2.1 from an USB stick through a floppy diskette quite well, but I can not boot Puppy 4.3.1 and 5.1.1.
OK, thanks for the feedback.I do not understand this suggestion about lower case.
I edited / clarified the above post, so hopefully now it will make more sense.
* Make a backup copy of your floppy's original AUTOEXEC.BAT file.how to replace the AUTOEXEC.BAT?
* Download the one I've posted above.
* Click on the file, then click on Select All, then Extract.
(You will need to choose directory where you want it to go.)
* Delete the floppy's original AUTOEXEC.BAT file and replace it with the new one.