Is a new boot floppy needed for Puppy 2.0 A4?

Message

Fox7777 · #1 Post by **Fox7777** » Thu 13 Apr 2006, 03:34

We are trying to install Puppy 2.0 A4 on some older computers that don't boot from the CD. We tried all the boot floppies incuding the latest WKPUP11C.IMG and couldn't get Puppy 2.0 A4 to boot. We know the pup.003.sfs is new and that might be the problem. The boot floppy did boot Puppy 1.0.8. Does a new boot floppy need to be created for Puppy 2.0 or is there a way to boot with an existng floppy?

BarryK · #2 Post by **BarryK** » Thu 13 Apr 2006, 08:38

Can you show some details of the boot floppies?
For example, if it has a config.sys or autoexec.bat, post the contents here.

Fox7777 · #3 Post by **Fox7777** » Thu 13 Apr 2006, 16:34

This is for the latest WakePup:

; CONFIG.SYS for WakePup v1.1c, (C) 26-Nov-05, Paul Akterstam.
; Menu structure from FreeDOS Beta 9 distro, http://www.fdos.org/
; v1.1c - removed USBASPI.SYS switch /w
;
!switches=/E
menucolor=7,0
menu ��
menu WakePup v1.1c Boot Menu (26-Nov-2005)
menu ��
menu
menu Boot Puppy from:
menu
menu 1. IDE/USB drives (built-in or external CD-ROM, HD and flash)
menu
menu 2. Iomega ZIP disk drive, connected to parallel port
menu
menu 3. Backpack CD-ROM drive, connected to parallel port
menu
menu 4. Addonics (or similar) CD-ROM drive, connected to PCMCIA
menu
menu ��
menudefault=1,30

; load VIDE v2.14 IDE/ATAPI CD-ROM device driver
1?!device=A:\driver\VIDE-CDD.SYS /d:IDE-CD

; enable USB mass storage devices (NEC OHCI/EHCI & Intel UHCI USB controllers)
; load Panasonic v2.20 ASPI manager for USB mass storage
; (maps USB mass storage devices to ASPI devices)
1?!device=A:\driver\usb\USBASPI.SYS /v

; load Panasonic v1.00 USB CD-ROM device driver
1?!device=A:\driver\usb\USBCD.SYS /d:USB-CD

; load NOVAC v2.00 ASPI disk driver
; DI1000DD.SYS hangs with USB flash, use ASPIDISK.SYS instead
;1?!device=A:\driver\DI1000DD.SYS

; load Adaptec v4.01b ASPI disk driver
; (maps ASPI mass storage devices to DOS drive letters)
1?!device=A:\driver\ASPIDISK.SYS

; load Micro Solutions v 4.02 BACKPACK CD-ROM device driver
3?!device=A:\driver\backpack\BPCDDRV.SYS /d:BP-CD

; load Shining v5.81 PMIDE-ASC, M17 Card Services Client
; Note: If using a VIA PCMCIA controller, add parameter "/V1" to next line
4?!device=A:\driver\pcmcia\PCMI80CL.SYS /QA
; load Shining v2.70 ATAPI/IDE CD-ROM device driver
4?!device=A:\driver\pcmcia\STATPCDM.SYS /Q0 /D:PCM-CD

1234?!SHELL=A:\COMMAND.COM A:\ /E:1024 /F /MSG /P=A:\AUTOEXEC.BAT

!files=20
!buffers=20
!lastdrive=Z
-------------------------------------------
@echo off
rem WakePup v1.1c, (C) 26-Nov-05, Paul Akterstam ('pakt' on Puppy Forum)
rem Inspired by Barry Kauler's BOOT2PUP (www.goosee.com/puppy)
rem
rem Requires FreeDOS & FreeCOM (%config% can have a value in range 0..9)
rem Uses SHSUCDX.COM, a freeware replacement for MSCDEX.EXE
rem Uses LINLD.COM with parameter file instead of TINY.EXE

rem This program is distributed in the hope that it will be useful, but
rem WITHOUT ANY WARRANTY; without even the implied warranty of
rem MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

rem Sections
rem (1) IDE/USB drives (built-in or external CD-ROM, HD and flash)
rem (2) Iomega ZIP drive, connected to parallel port
rem (3) Backpack CD-ROM drive, connected to parallel port
rem (4) Addonics (or similar) CD-ROM drive, connected to PCMCIA

echo.
if not "%config%"=="1" goto init
rem Pause here so USB driver messages can be read...
echo Pause for driver messages. Press any key to continue or Ctrl-C to abort...
pause >NUL

:init
cls
set pupdrv=
set cfg=
if "%config%"=="1" goto ideusb_drv
if "%config%"=="2" goto parzip_drv
if "%config%"=="3" goto parcd_drv
if "%config%"=="4" goto pcmcia_drv
goto end

:ideusb_drv
rem Section(1)
rem SHSUCDX assigns IDE CD-ROM to drive I:, USB CD-ROM to drive J:
driver\SHSUCDX /d:?IDE-CD,I /d:?USB-CD,J >NUL
echo Checking any IDE drive for marker file PUPXIDE...
for %%x in ( C D E F G H ) do if exist %%x:\pupxide set pupdrv=%%x:
if "%pupdrv%"=="" goto try_usb
set drvtype=IDE
goto ide_cd_common

:try_usb
echo.
echo Checking any USB drive for marker file PUPXUSB...
for %%x in ( C D E F G H ) do if exist %%x:\pupxusb set pupdrv=%%x:
if "%pupdrv%"=="" goto cd_drv
set drvtype=USB
goto usb_common

:parzip_drv
rem Section(2)
echo Looking for an Iomega parallel port ZIP drive...
driver\zipdrv\GUEST letter=I
echo Looking for marker file PUPXIDE...
if exist I:\pupxide set pupdrv=I:
if "%pupdrv%"=="" goto failed
set drvtype=ZIP
goto ide_cd_common

:parcd_drv
rem Section(3)
echo Looking for a Backpack parallel port CD-ROM drive...
rem SHSUCDX assigns parallel port CD-ROM to drive I:
driver\SHSUCDX /d:?BP-CD,I >NUL
goto cd_drv

:pcmcia_drv
rem Section(4)
rem Looking for an Addonics (or similar) PCMCIA CD-ROM drive...
rem SHSUCDX assigns PCMCIA CD-ROM to drive I:
driver\SHSUCDX /d:?PCM-CD,I >NUL
goto cd_drv

:cd_drv
echo.
echo Checking any CD-ROM drive for file IMAGE.GZ...
for %%x in ( I J ) do if exist %%x:\image.gz set pupdrv=%%x:
if "%pupdrv%"=="" goto failed
set drvtype=CD-ROM

:ide_cd_common
echo ...file found on %drvtype% drive %pupdrv%
echo.
echo ��
echo Select drive boot options
echo ��
echo
echo 1. PFILE=pup001-none-262144 (Default)
echo
echo 2. acpi=off PFILE=pup001-none-262144
echo
echo 3. PFILE=ask (choose pupxxx name & location)
echo
echo 4. acpi=off PFILE=ask (choose pupxxx name & location)
echo
echo ��
echo.
choice /C:1234 Enter a choice :
if "%errorlevel%"=="1" set cfg=IDECD1.CFG
if "%errorlevel%"=="2" set cfg=IDECD2.CFG
if "%errorlevel%"=="3" set cfg=IDECD3.CFG
if "%errorlevel%"=="4" set cfg=IDECD4.CFG
goto boot_drv

:usb_common
echo ...file found on USB drive %pupdrv%
echo.
echo ��
echo Select USB drive boot options
echo ��
echo
echo 1. PSLEEP=25 PHOME=sda1 PFILE=pup100-none-262144 (Default)
echo
echo 2. acpi=off PSLEEP=25 PHOME=sda1 PFILE=pup100-none-262144
echo
echo 3. PSLEEP=25 PFILE=ask (choose pupxxx name & location)
echo
echo 4. acpi=off PSLEEP=25 PFILE=ask (choose pupxxx name & location)
echo
echo ��
echo.
choice /C:1234 Enter a choice :
if "%errorlevel%"=="1" set cfg=USB1.CFG
if "%errorlevel%"=="2" set cfg=USB2.CFG
if "%errorlevel%"=="3" set cfg=USB3.CFG
if "%errorlevel%"=="4" set cfg=USB4.CFG

:boot_drv
echo.
LINLD.COM image=%pupdrv%\vmlinuz initrd=%pupdrv%\image.gz cl=@%cfg%
goto end

:failed
echo.
type FAILMSG.TXT

:end

pakt · #4 Post by **pakt** » Thu 13 Apr 2006, 18:17

Looks like it is time for me to adapt WakePup to Puppy2. I'll take a look at it in the next few days.

If Barry or anyone else has any suggestions, I welcome them

BTW, should we keep the options for booting from ancient hardware (parallel ZIP Drive/CD-ROM and PCMCIA CD-ROM) or should we just concentrate on booting from USB devices and IDE CD-ROM?

Paul

BarryK · #5 Post by **BarryK** » Fri 14 Apr 2006, 00:21

PSLEEP=25 PHOME=sda1 PFILE=pup100-none-262144
Yes, puppy2 will ignore these.
The only boot params that puppy2 recognises are PKEYS and PMEDIA.

PMEDIA is a description of the boot media. For example, if puppy is booting
from ide CD or DVD drive, then need PMEDIA=idecd.
Acceptable options:
PMEDIA=usbflash|usbhd|usbcd|ideflash|idehd|idecd|idezip|satahd|scsihd|scsicd
This parameter tells puppy2 where to look for the pup_xxx.sfs file (equiv of the usr_cram.fs file) and the first place to look for the saved session.

PMEDIA is actually optional, but then puppy has to look everywhere on pc to try and find the files.

pakt · #6 Post by **pakt** » Fri 14 Apr 2006, 12:30

Thanks for the summary, Barry.

If no one objects, I'll just make "WakePup2" boot USB and IDE drives - leave out the parallel/PCMCIA stuff.

I'll do some testing and post a "beta" soon.

Sit Heel Speak · #7 Post by **Sit Heel Speak** » Fri 14 Apr 2006, 17:13

pakt: please keep the PCMCIA CDROM boot option.

Sit Heel Speak · #8 Post by **Sit Heel Speak** » Sat 15 Apr 2006, 22:20

I have just successfully booted Puppy 2 alpha version 0.0.3 on my Thinkpad T21 from hard disk. vmlinuz, initrd.gz and so forth are in what Windows 98SE calls C:\ and I'm booting using grub, with "Boot Puppy" displayed as a menu option from c:\config.sys as described in the Puppy Linux Discussion Forum's Beginner's Help (Start Here) section thread "Need help installing pup on old IBM laptop" which is

http://www.murga.org/~puppy/viewtopic.php?t=7150

Booting time from power-on to desktop is 47 seconds. The SeaMonkey browser takes 5 seconds to load and is noticeably faster at calling up pages than Firefox in 1.0.8 was, though SeaMonkey doesn't seem to support wheelbutton auto-scrolling as Firefox does.

My menu.lst for grub is:

timeout 0
title Puppy from hard disk
rootnoverify (hd0,0)
kernel (hd0,0)/vmlinuz root=/dev/ram0 PSLEEP=25 PFILE=25 PFILE=pup100-none-131072 PHOME=hda1 PMEDIA=idehd
initrd (hd0,0)/initrd.gz
boot

("none-" etc. is on the same line as "kernel")

This menu.lst is edited just slightly (the PMEDIA= parameter added, and the directory in the kernel and initrd lines shifted from c:\boot to c:\) from the one I was using previously to boot Puppy 1.0.8 from flash drive. I am unsure how many of the "kernel" line parameters are necessary, and whether a PKEYS= statement should be put in there.

I have still not yet succeeded in booting Puppy 2 alpha from flash drive. I'm trying various permutations of both grub and the WakeUSB v0.1e boot floppy, both of which I previously booted Puppy 1.0.8 successfully from flash with. My Thinkpad's BIOS is too old to support direct booting from flash drive.

I will report on my booting experiments in the Puppy 2 forum.

Sit

pakt · #9 Post by **pakt** » Sun 16 Apr 2006, 07:15

Sit Heel Speak wrote:pakt: please keep the PCMCIA CDROM boot option.

Ok, I will keep the same boot options in WakePup2.

Sit Heel Speak, for booting from hd, instead of this line:

Code: Select all

kernel (hd0,0)/vmlinuz root=/dev/ram0 PSLEEP=25 PFILE=25 PFILE=pup100-none-131072 PHOME=hda1 PMEDIA=idehd

Use this one. Only 'PMEDIA' is necessary.

Code: Select all

kernel (hd0,0)/vmlinuz root=/dev/ram0 PMEDIA=idehd

For booting from USB, use:

Code: Select all

kernel (hd0,0)/vmlinuz root=/dev/ram0 PMEDIA=usbflash

Sit Heel Speak · #10 Post by **Sit Heel Speak** » Sun 16 Apr 2006, 11:10

Since pakt is the developer of WakeUSB, i.e. the mountain has come to Mohammed, I'll report here and hope that everyone sees it who needs to.

pakt:

By editing menu.lst as you suggest, I have booted Puppy 2 from grub on disk with vmlinuz et al on flash, with the flash drive plugged into the USB 1.1 port at the rear of the laptop. Booting time the 2nd session, after pup_save.3fs is present on the flash drive, is 1 minute 35 seconds, a 48-second slowdown from when Puppy is loaded from disk. The 1st time from flash it asked me the setup questions, so it wasn't reading pup_save.3fs from disk from my previous (inaugural, booted from disk) session.

I still cannot boot with the flash drive plugged into the much faster USB 2.0 PCMCIA Cardbus adapter, through the Thinkpad's PC Card slot. The USB device is not recognized and Puppy 2 flies into a kernel panic. Puppy 1.0.8 failed this test more gracefully, simply reporting it could not find usr_cram.fs but going ahead anyway and booting to a # prompt. My suspicion, based on study of Kethd's sticky post in Hardware, is that if I were to recompile the kernel to add the appropriate delay factor(s) into the kernel's probes when looking for USB devices and/or PCMCIA devices, in the order PCMCIA, USB, then perhaps I can make it work. Someday.

Upon shutdown Puppy 2 created pup_save.3fs in /dev/sda1, the flash drive. This took several minutes. I had a moment of panic when the screen went blank (black) long before pup_save.3fs was finished being written--ACPI works.

Booting to Windows, I see the size of pup_save.3fs on flash is 512MB, the same size as was created by my first (booted and loaded from disk) Puppy 2 session on C:\.

I wonder, is 512MB the default size of pup_save.3fs, or did Puppy 2 somehow learn that I had raised the size of pup100 in Puppy 1.0.8 to 512MB and, perhaps because booted from grub (the first time, from disk, as described above) which specified maximum pupfile size (PFILE=) of 512MB, make pup_save.3fs the same size as my old pup100 file? The file pup100 itself was not present, as I had erased it from the flash drive before loading the flash drive with the Puppy 2 files.

The automounting of devices differs between Puppy 1 and Puppy 2. When booting Puppy 1.0.8 from flash, using either a WakeUSB floppy or grub on disk, the contents of the physical topmost directory on flash were mounted automatically as /mnt/home and I had to mount the hard disk using PMount or MUT or manually in rxvt to see it.

In Puppy 2 booted using grub on disk and vmlinuz either way, on flash or on disk, I'm looking at a uXplor which shows neither /mnt/home nor /mnt/hda1 nor /mnt/sda1 present. I see in PMount that my flash drive is automounted as /initrd/mnt/dev_save if vmlinuz and initrd.gz are on flash, but not mounted at all if vmlinuz is on disk. Either way the hard disk is not automounted.

I can see where the inconsistent conventions by which the "home" device is mounted, between a flash installation and a disk installation, is going to cause headaches. Mounting the home device as /mnt/home no matter what its physical nature, as was done in Puppy 1.0.8, is a better idea and I would suggest to BarryK, unless someone can explain why it should not be so, that in Puppy 2 beta it go back to being this way.

An attempt to boot from grub-on-disk, to Puppy-on-disk, after running Puppy 2 from flash, failed. The boot came to a # prompt. I've learned enough now to mount the hard disk and run dmesg, outputting to a text file, from the # prompt, and did so. dmesg ends after four lines like

cs: IO port probe 0x0_00-0x0_ff: clean

except the third one ends in : excluding 0x170-0x177 0x370-0x377 0x4d0-0x4d7

Erasing pup_save.3fs from C:\ and starting over through the setup questions brought Puppy 2, grub-on-disk-and-vmlinuz-on-disk, back up OK. The pup_save.3fs on flash was not affected and booted OK in a subsequent try.

I still have not succeeded in booting Puppy 2 in flash, from the WakeUSB floppy.

My impression of Puppy 2 at this point is, the default installation's look is cleaner, fonts are nicer, and it's preferable to Puppy 1 for computers which are RAM-challenged. And because personal storage is all permanent it's a better development environment, and it's safer for us new users than Puppy 1. However the volatility of Puppy 1 lends itself to better security than Puppy 2, when run from flash.

And so, Puppy 2 is my development environment while Puppy 1 will be what I carry with me for day-to-day professional use.

pakt · #11 Post by **pakt** » Tue 18 Apr 2006, 08:48

Sit Heel Speak wrote:Since pakt is the developer of WakeUSB, i.e. the mountain has come to Mohammed, I'll report here and hope that everyone sees it who needs to.

Flattery will get you everywhere

Actually, I should make a little clarification here. There are two Puppy boot floppies I have made: WakePup and WakeUSB.

WakePup was a re-write and improvement of BarryK's BOOT2PUP floppy, and I included booting from "lagging-edge" legacy devices I had laying around: a parallel ZIP drive, a PCMCIA CD-ROM and a Backpack parallel CD-ROM.

WakeUSB was a spin-off from WakePup that only booted USB devices. It was experimental in that it could find and read the ramdisk_size parameter from either the CD's isolinux.cfg file or a USB device's syslinux.cfg file. I put that in to accomodate non-standard Puppies like ChubbyPuppy and PizzaPup which had custom ramdisk_size parameters that WakePup could not boot. It also had a limited built-in parameter editor to allow adjustments before booting. WakePup's drawback was that I was forced to use a DOS ramdisk to save partial results in files. That in turn required a DOS memory manager. You may remember from the old DOS days that memory managers didn't always work with all hardware. Well, WakeUSB doesn't work on all PCs for that reason. WakePup doesn't use these touchy DOS utilities and therefore works more reliably.

Sit Heel Speak wrote: By editing menu.lst as you suggest, I have booted Puppy 2 from grub on disk with vmlinuz et al on flash, with the flash drive plugged into the USB 1.1 port at the rear of the laptop. Booting time the 2nd session, after pup_save.3fs is present on the flash drive, is 1 minute 35 seconds, a 48-second slowdown from when Puppy is loaded from disk. The 1st time from flash it asked me the setup questions, so it wasn't reading pup_save.3fs from disk from my previous (inaugural, booted from disk) session.

Nice work. I haven't tried booting from a flash drive via grub-on-hd yet. The times you are getting are of course (as you imply) due to the slow transfer speed of USB1.1.

Sit Heel Speak wrote: I still cannot boot with the flash drive plugged into the much faster USB 2.0 PCMCIA Cardbus adapter, through the Thinkpad's PC Card slot. The USB device is not recognized and Puppy 2 flies into a kernel panic. Puppy 1.0.8 failed this test more gracefully, simply reporting it could not find usr_cram.fs but going ahead anyway and booting to a # prompt. My suspicion, based on study of Kethd's sticky post in Hardware, is that if I were to recompile the kernel to add the appropriate delay factor(s) into the kernel's probes when looking for USB devices and/or PCMCIA devices, in the order PCMCIA, USB, then perhaps I can make it work. Someday.

Yes, I had the same problem when I was testing WakePup with my Belkin 2-port USB2.0 Cardbus adapter in my ThinkPad T20. IIRC, it was necessary to use an external power adapter with the Belkin adapter for WakePup to see the USB devices. The problem is, as you correctly point out, that Puppy doesn't detect the USB device properly during booting.

Sit Heel Speak wrote: I wonder, is 512MB the default size of pup_save.3fs, or did Puppy 2 somehow learn that I had raised the size of pup100 in Puppy 1.0.8 to 512MB and, perhaps because booted from grub (the first time, from disk, as described above) which specified maximum pupfile size (PFILE=) of 512MB, make pup_save.3fs the same size as my old pup100 file? The file pup100 itself was not present, as I had erased it from the flash drive before loading the flash drive with the Puppy 2 files.

I believe Barry made pup_save.3fs default to 512MB, but will shrink to accomodate smaller flash devices, leaving 8MB free space.

Sit Heel Speak wrote: An attempt to boot from grub-on-disk, to Puppy-on-disk, after running Puppy 2 from flash, failed. The boot came to a # prompt.

If you had typed

# xwin

at this point, I think X would have started along with JWM giving you a working Puppy. That X doesn't start automatically here seems to be a bug because it happens to me too when rebooting Puppy2 - I only get a # prompt and have to type 'xwin' to start X.

Sit Heel Speak wrote: I still have not succeeded in booting Puppy 2 in flash, from the WakeUSB floppy.

I am working on WakePup2 and have so far succeded in getting it to boot from 'idecd' and 'usbflash'. I may release an early test version today or tomorrow with the PCMCIA/parallel choices not yet working.

Paul

Sit Heel Speak · #12 Post by **Sit Heel Speak** » Tue 18 Apr 2006, 11:28

Hmmm. Why isn't "quote" working for me?...

[quote="pakt"]WakePup was a re-write and improvement of BarryK's BOOT2PUP floppy, and I included booting from "lagging-edge" legacy devices I had laying around: a parallel ZIP drive, a PCMCIA CD-ROM and a Backpack parallel CD-ROM.

WakeUSB was a spin-off from WakePup that only booted USB devices.[/quote]

So that is the reason why I can boot a flash key with WakeUSB but not boot2pup or wakepup...

[quote="pakt"]...with my Belkin 2-port USB 2.0 Cardbus adapter in my ThinkPad T20...IIRC, it was necessary to use an external power adapter with the Belkin adapter for WakePup to see the USB devices...[/quote]

Some USB flash keys require external power, some don't (i.e. they run from the current supplied by the USB port). In Windows 98SE, I can use my SanDisk Cruzer Mini 2GB flash key in my Hewlett-Packard PM453A 2-port USB 2.0 Cardbus adapter (probably identical on the inside to your Belkin, with NEC EHCI chipset) without the need to connect external power. The Ars-Technica website did reviews in 2004 and 2005 of USB flash keys. They found, IIRC, a total of four model lines which like my SanDisk do not require external power.

[quote="pakt"]The problem is, as you correctly point out, that Puppy doesn't detect the USB device properly during booting.[/quote]

Yes, but I wonder whether this is something which needs kernel-recompilation to fix, or whether it can be solved in the init script(s). I haven't looked at them closely yet.

[quote="pakt"]I believe Barry made pup_save.3fs default to 512MB, but will shrink to accomodate smaller flash devices, leaving 8MB free space.[/quote]

Yes, I see that, now that I have read "How Puppy Works."

I wonder whether it might improve performance to retain the ramdisk layer when booting to the Pupmode of installation option 1, the hard disk non-invasive method which I've used. Professor Kauler seems to have things set up so that there is no ramdisk layer on top, instead the persistent storage is mounted topmost in the unionfs "layer-cake." I wonder whether this means that the speed of program startups is limited by my hard disk speed.

I also wonder how I can make Fedora Bordeaux 5 be my "underdog" layer...

[quote="pakt"]I am working on WakePup2 and have so far succeeded in getting it to boot from 'idecd' and 'usbflash'. I may release an early test version today or tomorrow with the PCMCIA/parallel choices not yet working.[/quote]

I look forward to trying this.

pakt · #13 Post by **pakt** » Tue 18 Apr 2006, 19:00

Sit Heel Speak wrote:Hmmm. Why isn't "quote" working for me?...

Could it be that you have disabled 'Always allow BBCode' in your forum profile? I'm not sure what this does, but I have 'yes' on it.

As to WakePup2, I've got 'idecd', 'usbflash' and 'usbcd' working now.

Sit Heel Speak wrote:pakt: please keep the PCMCIA CDROM boot option.

I think I have bad news for you here. I tested using my Addonics PCMCIA CD-ROM but couldn't get Puppy2 to boot from it. By watching the boot messages, I saw that the 'Linux Kernel Card Services 3.1.22' code runs after Puppy2 tries to read its files from the IDE CD-ROMs it has found. It ends up with:

Code: Select all

ERROR, cannot find Puppy on idecd boot media.
PUPMODE=9  PDEV=
Kernel panic: ... <and the PC halts at this point>

Paul

Sit Heel Speak · #14 Post by **Sit Heel Speak** » Tue 18 Apr 2006, 19:15

pakt wrote:Could it be that you have disabled 'Always allow BBCode' in your forum profile? I'm not sure what this does, but I have 'yes' on it.

I've now turned on BBCode, let's see if that was the problem.

pakt wrote:
Sit Heel Speak wrote:pakt: please keep the PCMCIA CDROM boot option.
I think I have bad news for you here. I tested using my Addonics PCMCIA CD-ROM but couldn't get Puppy2 to boot from it. By watching the boot messages,...

The reason why I suggested keeping the PCMCIA CDROM boot option was, I thought that perhaps by formatting my USB flash key as a CDROM I might trick Puppy into booting from it through the PCMCIA card.

But, if the Card Services runs _after_ the search for bootable CDROM code, then my idea comes to nought.

...so the question, I presume, is, how do we make the Card Services kernel code run earlier?

pakt · #15 Post by **pakt** » Wed 19 Apr 2006, 18:21

Sit Heel Speak, I have decided to put WakePup2 on hold for now. This is due to Barry's possible switch to the 2.6 kernel.

See the thread http://www.puppyos.com/nfphpbb/viewtopic.php?t=94 in the Puppy2 forum and Barry's news for April 19.

Paul

Sit Heel Speak · #16 Post by **Sit Heel Speak** » Wed 19 Apr 2006, 23:34

pakt:

It is my understanding that USB is much better supported in the 2.6 kernel than in 2.4, so that move alone may fulfill my wish. Thanks for the heads-up.

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

Is a new boot floppy needed for Puppy 2.0 A4?

Is a new boot floppy needed for Puppy 2.0 A4?

Re: Is a new boot floppy needed for Puppy 2.0 A4?

I too can't make Puppy 2 boot from floppy but can with grub