Puppy Linux Windows Users: exe installer programs
Regarding PROBLEM3:
1. A WakePup2 floppy made using the normal method within BoxPup exhibits the same problem symptoms.
e.g.
(a) I formatted a floppy within BoxPup.
(b) Used the WakePup2 program to write the necessary files to the floppy.
(c) Rebooted with the floppy in its drive, and the USB Flash Drive in place.
(d) The blue LED on the Flash Drive was constantly lit and unblinking.
(e) The process twice halted immediately prior to the point where the Puppy files are loaded off the Flash Drive.
[I hit Ctrl+Alt+Del to restart]
(f) At some point during the 2nd attempt, the blue LED began flashing.
I knew from past experience that this is a good sign, and I could now expect success at the next attempt.
(g) At the beginning of the 3rd attempt, the LED was unblinking, but at a certain point it began blinking, and the files began loading, and Puppy booted successfully.
2. Is this a problem with my hardware or what?
3. I notice that on a neighbours PC...
[I'm showing him Puppy booting from an optical disk and Flash Drive, on his PC]
When the identical boot process got to the same point [of loading the files off the Flash Drive], his PC gives a constant/unvarying [rather quiet] beep tone.
Sound like a warning of something.
His PC's BIOS [like mine] doesn't support booting USB.
1. A WakePup2 floppy made using the normal method within BoxPup exhibits the same problem symptoms.
e.g.
(a) I formatted a floppy within BoxPup.
(b) Used the WakePup2 program to write the necessary files to the floppy.
(c) Rebooted with the floppy in its drive, and the USB Flash Drive in place.
(d) The blue LED on the Flash Drive was constantly lit and unblinking.
(e) The process twice halted immediately prior to the point where the Puppy files are loaded off the Flash Drive.
[I hit Ctrl+Alt+Del to restart]
(f) At some point during the 2nd attempt, the blue LED began flashing.
I knew from past experience that this is a good sign, and I could now expect success at the next attempt.
(g) At the beginning of the 3rd attempt, the LED was unblinking, but at a certain point it began blinking, and the files began loading, and Puppy booted successfully.
2. Is this a problem with my hardware or what?
3. I notice that on a neighbours PC...
[I'm showing him Puppy booting from an optical disk and Flash Drive, on his PC]
When the identical boot process got to the same point [of loading the files off the Flash Drive], his PC gives a constant/unvarying [rather quiet] beep tone.
Sound like a warning of something.
His PC's BIOS [like mine] doesn't support booting USB.
Are you using acpi=off option? Or pci=noacpi?
I remembered just now that on my old laptopn I had a similar problem with 4.3.1.
I solved it by using one of that options to boot correctly and I needed to had xorgwizard rightly finished to see the question about saving on shutdown.
I remembered just now that on my old laptopn I had a similar problem with 4.3.1.
I solved it by using one of that options to boot correctly and I needed to had xorgwizard rightly finished to see the question about saving on shutdown.
T_Hobbit
:idea: Rebuilding old DOS Machine for Wing Commander Privateer and Puppy :!: Old spare parts to give away - anyone interested :?:
:idea: Rebuilding old DOS Machine for Wing Commander Privateer and Puppy :!: Old spare parts to give away - anyone interested :?:
1. "Are you using acpi=off option? Or pci=noacpi?"
(a) I don't even know what that means.
OK, looked it up in Wikipedia.
That's enabled in my PC's BIOS I believe, and so far as I know no configuration has been made to switch it off in any Puppy.
I have it enabled in Win2000Pro.
(b) I have never previously had PROBLEM3 with any Puppy I've ever run; this is the only one.
Mind you, Puppy 4.2.1-rc3 is the only other I run from a Flash Drive, and it has always saved normally.
(a) I don't even know what that means.
OK, looked it up in Wikipedia.
That's enabled in my PC's BIOS I believe, and so far as I know no configuration has been made to switch it off in any Puppy.
I have it enabled in Win2000Pro.
(b) I have never previously had PROBLEM3 with any Puppy I've ever run; this is the only one.
Mind you, Puppy 4.2.1-rc3 is the only other I run from a Flash Drive, and it has always saved normally.
The new Puppy versions have a kernel that doesn't work that good with old hardware.
Edit your syslinux.cfg and you must see something like
Add acpi=off to the end. If it doesn't work, try pci=noacpi.
Remember that if you xorgvesa, you must finish the selection by pressing "done" (or whatever "say" the other button but "change"...).
Edit your syslinux.cfg and you must see something like
Code: Select all
default vmlinuz initrd=initrd.gz pmedia=usbflash fastboot
Remember that if you xorgvesa, you must finish the selection by pressing "done" (or whatever "say" the other button but "change"...).
T_Hobbit
:idea: Rebuilding old DOS Machine for Wing Commander Privateer and Puppy :!: Old spare parts to give away - anyone interested :?:
:idea: Rebuilding old DOS Machine for Wing Commander Privateer and Puppy :!: Old spare parts to give away - anyone interested :?:
Here's the contents of my syslinux.cfg
What do you think this aught to be changed to?
What do you think this aught to be changed to?
Code: Select all
default puppy
display boot.msg
prompt 1
timeout 50
F1 boot.msg
F2 help.msg
label puppy
kernel vmlinuz
append initrd=initrd.gz pmedia=cd
Sylvander: yeah, it's a hardware issue. That's the adventure of WakePup2 is it is a little different on different hardware. In other words, I am posting this from one of the computers at work, WakePup works great usb saves, etc.
At home, WakePup2 works different on different computers that I have, one I've gotta hit 5, the other just enter, one won't work with that usb at all on that pc, etc.
Sounds like T_Hobbit is giving you good instruction, though.
I am thinking of also making a boot cd exe....but one thing at a time...
At home, WakePup2 works different on different computers that I have, one I've gotta hit 5, the other just enter, one won't work with that usb at all on that pc, etc.
Sounds like T_Hobbit is giving you good instruction, though.
I am thinking of also making a boot cd exe....but one thing at a time...
Try
or
If the computer still "beep" along the way, try also the "quiet" option (add quiet to the end of that line)... Just to check!
Code: Select all
append initrd=initrd.gz pmedia=usbflash acpi=off
Code: Select all
append initrd=initrd.gz pmedia=usbflash pci=noacpi
T_Hobbit
:idea: Rebuilding old DOS Machine for Wing Commander Privateer and Puppy :!: Old spare parts to give away - anyone interested :?:
:idea: Rebuilding old DOS Machine for Wing Commander Privateer and Puppy :!: Old spare parts to give away - anyone interested :?:
Not replace. Add to the line.Sylvander wrote:Tried replacing the existing line of code beginning append, first with the top line you supplied, then with the bottom, but neither made any difference.
My PC doesn't beep, so no need to add that in my own case.
T_Hobbit
:idea: Rebuilding old DOS Machine for Wing Commander Privateer and Puppy :!: Old spare parts to give away - anyone interested :?:
:idea: Rebuilding old DOS Machine for Wing Commander Privateer and Puppy :!: Old spare parts to give away - anyone interested :?:
1. "Not replace. Add to the line."
(a) What I did was to replace...
with this...
Then instead with this...
(b) Surely you don't mean the line of code should look like this...
Or this...
(a) What I did was to replace...
Code: Select all
append initrd=initrd.gz pmedia=cd
Code: Select all
append initrd=initrd.gz pmedia=usbflash acpi=off
Code: Select all
append initrd=initrd.gz pmedia=usbflash pci=noacpi
Code: Select all
append initrd=initrd.gz pmedia=cd append initrd=initrd.gz pmedia=usbflash acpi=off
Code: Select all
append initrd=initrd.gz pmedia=cd append initrd=initrd.gz pmedia=usbflash pci=noacpi
Yes, you're right. I shall not make a post when I'm sleepy!
I've been wondering... Wakepup make use of syslinux.cfg on the flash drive...?
I never use wakepup but... probably the boot option must be changed on the wakepup floppy instead...
I've been wondering... Wakepup make use of syslinux.cfg on the flash drive...?
I never use wakepup but... probably the boot option must be changed on the wakepup floppy instead...
T_Hobbit
:idea: Rebuilding old DOS Machine for Wing Commander Privateer and Puppy :!: Old spare parts to give away - anyone interested :?:
:idea: Rebuilding old DOS Machine for Wing Commander Privateer and Puppy :!: Old spare parts to give away - anyone interested :?:
Old computer, right? We are using Puppy 4.3.1, right?Sylvander wrote:(b) I have never previously had PROBLEM3 with any Puppy I've ever run; this is the only one.
Mind you, Puppy 4.2.1-rc3 is the only other I run from a Flash Drive, and it has always saved normally.
I had this problem booting old laptop with the normal 4.3 and 4.3.1. I solved the problem turning to old kernel versions...
T_Hobbit
:idea: Rebuilding old DOS Machine for Wing Commander Privateer and Puppy :!: Old spare parts to give away - anyone interested :?:
:idea: Rebuilding old DOS Machine for Wing Commander Privateer and Puppy :!: Old spare parts to give away - anyone interested :?:
1. "Old computer, right?"
Correct.
Compaq Deskpro EN built 1999.
2. "We are using Puppy 4.3.1, right?"
Correct.
3. "I had this problem booting old laptop with the normal 4.3 and 4.3.1"
I had trouble with 4.3-k2.6.30.5, so had to use k2.6.25.16 which worked OK.
I use ttuuxxx's retro version of 4.31.1, and that works well.
Normally the problem I'd see is that the problem Puppy couldn't see my HDD, because it's connected via a PCI to IDE SCSI RAID controller card.
Correct.
Compaq Deskpro EN built 1999.
2. "We are using Puppy 4.3.1, right?"
Correct.
3. "I had this problem booting old laptop with the normal 4.3 and 4.3.1"
I had trouble with 4.3-k2.6.30.5, so had to use k2.6.25.16 which worked OK.
I use ttuuxxx's retro version of 4.31.1, and that works well.
Normally the problem I'd see is that the problem Puppy couldn't see my HDD, because it's connected via a PCI to IDE SCSI RAID controller card.