USB booting :: USB boot compatability list

Notebook computer - HP Pavilion ZE5610CA.
USB Flashdrive - 128 Meg UniversalSmartDrive

Changed Boot order in Bios so that USB is before the Harddrive.

Bill

hi!

Transcend JetFlash Mini 256MB - works perfect.

USB Stick preparation:
I used the WinImage method, described elsewhere in this forum, so I was able to prepare the USB Stick completely from within Windows. Just one point:
I had to use bootusb-0.8 with dsl-0.9.3-syslinux.iso instead of dsl-0.9.3.iso, because the boot image also seems to use syslinux. I also tried dsl-0.9.3.iso, but it didn't work for me ("KNOPPIX filesystem not found..." or so).

System preparation:
I use a ASUS P5GD1 with AMI BIOS v1007.
Steps required to boot from USB Stick:
1) insert prepared USB stick
2) reboot and enter BIOS (press "Del" at boot time)
3) Enter the "Boot" Menu. If your Stick is correctly prepared, a Sub menu "Removable Drives" will appear. Enter it.
4) Be sure to set "1st Drive" to "JetFlash"
5) Leave Sub menu "Removable Drives"
6) Enter Sub menu "Boot Device Priority"
7) Be sure, "[JetFlash]" appears in the list. Adjust boot priority, so the PC will boot from JetFlash instead of HDD.
8) Thats it. Leave BIOS by pressing "F10" and "Enter". Your system should now boot from the USB Stick.

System issues:
My SATA-HDD is not recognized.
The P5GD1 features an on-board Marvell Yukon PCI Express Gigabit Network Adapter, which seems not to be supported by DSL out of the box. Anyway, The Driver is available from Marvell (sk98lin), though I didn't have had the time yet to compile and test it.

Regards,
Andreas

HP zd7020us works fine with DSL embedded 1.01rc using a Kingston DataTraveler II Plus. You have to insert the pendrive, go into the BIOS, setup the boot sequence (the USB drive appears as a hard drive), and you are ready to go.

My Sandisk Cruzer Titanium 512MB USB 2.0 works fine with DSL. Just one little problem, the Cruzer PocketCache program (synchronisation tool for Win) did only run in evaluation mode (90 days!) when it was started from the Cruzer. Sandisk Customer Support have arranged a replacement as the program should run without any restrictions.

I suspect that the device has an identifier that is overwritten when DSL is loaded on it. I've looked at the MBR of the new Cruzer but haven't found any obvious identifiers.

(For completeness, I was using SLAX on the Cruzer as well so that might have overwritten something too.)

Has anyone seen this before?

It probably uses something like the volume label of the driver partition as a kind of Serial Number.

It may be possible to keep this information intact if you "sys" the existing partition with syslinux instead of overwriting the whole thing.

Next Page...
original here.