Frontpage
Forums
Tutorials
Members
Calendar
Subscription
Donate
Links
Contact 
Help
The Boss Man really wants to boot WinPE from USB Key drives. I've given him the information from Microsoft saying it won't work, but he doesn't believe that it is impossible. (In other words, I have to continue trying until either Microsoft supports it, or I find some kind of a work around) Right now, I'm looking at IDE to USB adapters. We've all seen the IDE to Compact Flash adapters that will run Linux, but has anyone tried using the adapter that is IDE female on one end to USB B on the other end with a USB gender adapter to allow for a USB Key drive to plug into it? I know this is a long shot, but I have to be fairly certain on these things before I go out and buy a $60 adapter that might just go to waste. Thanks.
Boot PE from USB Flash Drive
Rate Topic:
Back to top
#2
- Ditchy McAbandonpants
-
- Group: Members
- Posts: 946
- Joined: 27-January 04
Posted 03 September 2004 - 10:07 AM
i think there was a way to get it boot from usb hard drive, so adapting it to run off flash drive shouldnt be that hard...dunno where that thread went...also, id await the sp2 release of winpe.
#3
Posted 04 September 2004 - 02:22 AM
Hi,
I got it booted from an USB Stick and some Boards that have an Award Bios where you can choose the emulation mode for usb (you must be able to emulate as hdd).
than you can use a hp tool to partitioning and formatting the stick fat16 (i do not know the web adress at the moment from the tool).than copy the i386 dir to the stick and rename i386 to minint.Then copy ntdetect.com to the root and setupldr.bin to the root.rename setupldr.bin to ntldr.And set the stick active (thats normally done if you used the hp tools).after all that it should boot on some mainboards (not all).
there was a big thread on the 911 forum thats closed at the moment.
keep up
dicht
I got it booted from an USB Stick and some Boards that have an Award Bios where you can choose the emulation mode for usb (you must be able to emulate as hdd).
than you can use a hp tool to partitioning and formatting the stick fat16 (i do not know the web adress at the moment from the tool).than copy the i386 dir to the stick and rename i386 to minint.Then copy ntdetect.com to the root and setupldr.bin to the root.rename setupldr.bin to ntldr.And set the stick active (thats normally done if you used the hp tools).after all that it should boot on some mainboards (not all).
there was a big thread on the 911 forum thats closed at the moment.
keep up
dicht
#4
- Advanced Member
-
- Group: Members
- Posts: 309
- Joined: 14-June 04
Posted 07 September 2004 - 10:10 AM
I had problems with the USB ports getting initialized just before logon and throwing BSOD Mass Storage failures
#5
Posted 10 September 2004 - 02:16 PM
All good ideas. I think we are just going to have to wait for the industry to support the concept better before we can put this into production. The problem with leaving the Key Drive in Fat is that our HDDs are all NTFS, so we would not be able to do any type file recovery, which is large part of what we see this being used for.
#6
- Member
-
- Group: Members
- Posts: 186
- Joined: 09-January 04
Posted 10 September 2004 - 04:39 PM
If you had a large enough key you could always partition it so the PE partition was fat and bootable but then you had a storage partition that was NTFS. I think 1GB USB Keys are going for around ~$150 now (SanDisk Cruzer Mini), so I guess it would be feasable.
Cheers
Cheers
#7
Posted 16 September 2004 - 01:54 AM
I managed to get this working yesterday using dicht's method. 
Make sure you use FAT16 as the file system on the usb key. Use the HP tool (which is available as a download on their website listed under most of their new PCs drivers). That makes the partition active. Copy all of your working PE cd to the USB key. Copy ntdetect.com from the i386 dir into the root dir on the key, and copy setupldr.bin from the i386 dir to ntldr in the root dir too (no extension on ntldr file). Rename i386 to minint and it should boot.
Make sure you use FAT16 as the file system on the usb key. Use the HP tool (which is available as a download on their website listed under most of their new PCs drivers). That makes the partition active. Copy all of your working PE cd to the USB key. Copy ntdetect.com from the i386 dir into the root dir on the key, and copy setupldr.bin from the i386 dir to ntldr in the root dir too (no extension on ntldr file). Rename i386 to minint and it should boot.
#8
Posted 21 September 2004 - 06:26 AM
Mallen, were you able to access information on NTFS drives?
#9
- [Centos~]$
-
- Group: Members
- Posts: 960
- Joined: 16-September 03
Posted 21 September 2004 - 08:09 AM
Has anyone used NTFS for DOS from winPE on FAT16? This might work, you would need to add DOS support to WinPE though. There is a post 911CD.net that tells how to do it. Just a thought.
#10
Posted 27 September 2004 - 10:29 AM
why would you need ntfs for DOS in winpe. Winpe is supposed to have native support for NTFS. Or maybe I didn't understand it right. there is a guide around this forun on how to get Dos applications to work on winpe. Applications that need direct access to the hardware don't work though. (Protected Mode, same as XP)
I think the post is called Porting Dos Applications to Winpe.
EDIT
Porting Dos Applications on WinPe
I think the post is called Porting Dos Applications to Winpe.
EDIT
Porting Dos Applications on WinPe
#11
- [Centos~]$
-
- Group: Members
- Posts: 960
- Joined: 16-September 03
Posted 27 September 2004 - 01:43 PM
Right it does but, he is thinking of having the fat16 filesystem on his USB stick, and from what i gathered, I could be wrong since I never used it, but using fat16 as a FS and trying to access NTFS doesn't work. So in turn if he ran NTFS for Dos in theory he should be able to access NTFS from a FAT16 FS. Just a thought as I said before I have never used NTFS for Dos nor WinPE on a FAT16 FS. So anyone who has is more than welcome to sort this out.
#12
- The Finder
-
- Group: Developers
- Posts: 11,408
- Joined: 23-July 04
- OS:none specified
-
Country:
Posted 27 September 2004 - 04:46 PM
@likuidkewl
I don't want to seem a teacher, but from your post it seems like you make some confusion between Operating System and File system.
A file system is just a "convention" about how data should be stored on various memory devices.
More properly, a file system is a protocol about storing data, to access this protocol, an Operating System needs an interpreter, i.e. in this case a "filesystem driver".
You assign a filesystem to a drive when you format it, i.e. you give it the structure according to the chosen protocol.
Filesystem drivers are divided in two classes:
-NATIVE ones (build in)
-ADDONS (external)
DOS up to 6.22 has just two native filesystem drivers: FAT12 (floppies) and FAT16 (Hard disks and the like)
Windows 95 1st edition has the same filesystem drivers.
Windows NT 3.51 and 4.00 have the same as above + NTFS (v4)
Windows 95 OEM2, Windows 98 (1st and SE) and Windows Millennium have the same as DOS + FAT32
Windows 2000, XP, 2003, BartPE and WinPE have the same as above + NTFS (v5) (not backward compatible with NTFS v4 and partially supported by Windows NT Service Pack 3+)
Excluding FAT12 (for size problems), any Operating System can be installed on any filesystem supported by self NATIVE filesystem drivers, and can access any other NATIVE filesystem.
NTFSDOS is an ADDON filesystem driver, this means that you cannot install DOS on a NTFS filesystem, as it cannot read data BEFORE loading the ADDON.
There is (or better was) a similar driver for Windows NT 4.00 which gave access to FAT32 volumes, again you cannot install NT on a FAT32 partition.
There is (or better was) a similar driver for Windows 98 which gave access to NTFS volumes, again you cannot install 98 on a NTFS partition.
There are drivers for all windows to access EXT2 partitions (a LINUX filesystem), and for many others.
The boot problem in previous posts depends on the way the motherboard BIOS deals with USB Memory Sticks, there is no reason (theoretically) on why a system can boot a "drive" if formatted as FAT16 and cannot boot another one formatted FAT32 or NTFS (or any other filesystem provided its driver is NATIVE to the OS), unless BIOS programmers made some "shotcuts" in the BIOS routine that handles the device.
A proof of this is that this guy here has succeeded in booting linux from an EXT2 formatted USB stick:
http://www.ibiblio.org/pub/Linux/docs/HOWT...mory-HOWTO.html
From here:
http://www.marlow.dk...hp/tech/usbkeys
So if you can (i.e. your motherboard supports) the "hardisk" format, and the USB stick is formatted accordingly, you can get a bootable USB stick with ANY filsystem, if it does not, you are stuck to FAT16.
Hope the above clears the matter.
jaclaz
Quote
but using fat16 as a FS and trying to access NTFS doesn't work. So in turn if he ran NTFS for Dos in theory he should be able to access NTFS from a FAT16 FS.
A file system is just a "convention" about how data should be stored on various memory devices.
More properly, a file system is a protocol about storing data, to access this protocol, an Operating System needs an interpreter, i.e. in this case a "filesystem driver".
You assign a filesystem to a drive when you format it, i.e. you give it the structure according to the chosen protocol.
Filesystem drivers are divided in two classes:
-NATIVE ones (build in)
-ADDONS (external)
DOS up to 6.22 has just two native filesystem drivers: FAT12 (floppies) and FAT16 (Hard disks and the like)
Windows 95 1st edition has the same filesystem drivers.
Windows NT 3.51 and 4.00 have the same as above + NTFS (v4)
Windows 95 OEM2, Windows 98 (1st and SE) and Windows Millennium have the same as DOS + FAT32
Windows 2000, XP, 2003, BartPE and WinPE have the same as above + NTFS (v5) (not backward compatible with NTFS v4 and partially supported by Windows NT Service Pack 3+)
Excluding FAT12 (for size problems), any Operating System can be installed on any filesystem supported by self NATIVE filesystem drivers, and can access any other NATIVE filesystem.
NTFSDOS is an ADDON filesystem driver, this means that you cannot install DOS on a NTFS filesystem, as it cannot read data BEFORE loading the ADDON.
There is (or better was) a similar driver for Windows NT 4.00 which gave access to FAT32 volumes, again you cannot install NT on a FAT32 partition.
There is (or better was) a similar driver for Windows 98 which gave access to NTFS volumes, again you cannot install 98 on a NTFS partition.
There are drivers for all windows to access EXT2 partitions (a LINUX filesystem), and for many others.
The boot problem in previous posts depends on the way the motherboard BIOS deals with USB Memory Sticks, there is no reason (theoretically) on why a system can boot a "drive" if formatted as FAT16 and cannot boot another one formatted FAT32 or NTFS (or any other filesystem provided its driver is NATIVE to the OS), unless BIOS programmers made some "shotcuts" in the BIOS routine that handles the device.
A proof of this is that this guy here has succeeded in booting linux from an EXT2 formatted USB stick:
http://www.ibiblio.org/pub/Linux/docs/HOWT...mory-HOWTO.html
From here:
http://www.marlow.dk...hp/tech/usbkeys
Quote
USB Keys can be formatted in two ways:
Superfloppy
Harddisk (including MBR)
This is the reason, why some bootable USB keys not boot on every system. Some computers BIOS simply only understand one of the formats, not both, and if you use Windows and plug your key in, you won't notice the difference. Using Linux it get's pretty clear. Looking at the different formats shows, that the superfloppy formatted key is formatted as one big storage device (/dev/sda is mounted). The harddisk formatted key, which has a MBR, can have multiple partitions (/dev/sda1 etc.).
Superfloppy
Harddisk (including MBR)
This is the reason, why some bootable USB keys not boot on every system. Some computers BIOS simply only understand one of the formats, not both, and if you use Windows and plug your key in, you won't notice the difference. Using Linux it get's pretty clear. Looking at the different formats shows, that the superfloppy formatted key is formatted as one big storage device (/dev/sda is mounted). The harddisk formatted key, which has a MBR, can have multiple partitions (/dev/sda1 etc.).
So if you can (i.e. your motherboard supports) the "hardisk" format, and the USB stick is formatted accordingly, you can get a bootable USB stick with ANY filsystem, if it does not, you are stuck to FAT16.
Hope the above clears the matter.
jaclaz
#13
- [Centos~]$
-
- Group: Members
- Posts: 960
- Joined: 16-September 03
Posted 27 September 2004 - 05:17 PM
Thanks for clearing up my brain fart.
#14
- pope of preinstall. wizard of winpe. bender of things.
-
- Group: Members
- Posts: 51
- Joined: 18-October 04
Posted 19 October 2004 - 11:32 AM
For the record: Microsoft has announced that they're going to officially support booting from USB Disk On Key things in the Server 2003 SP1 release.
#15
- Junior
-
- Group: Members
- Posts: 87
- Joined: 07-June 04
Posted 21 October 2004 - 08:55 AM
Hy everyone!
I'm having a little problem with the boot.
I use the HP tool to format my USB key with this command line syntax:
Then...I copy all the files of a Windows PE 1.2 cd and make the necessary changes explained on this thread.
When I put the USB Key on the computer and boot from it, it boots but doesn't launch WinPE. Just the DOS Prompt.
Any ideas?
I'm having a little problem with the boot.
I use the HP tool to format my USB key with this command line syntax:
HPUSBF.EXE HD3 -Q -B:C:\DOSFILES
Then...I copy all the files of a Windows PE 1.2 cd and make the necessary changes explained on this thread.
When I put the USB Key on the computer and boot from it, it boots but doesn't launch WinPE. Just the DOS Prompt.
Any ideas?
#16
- The Finder
-
- Group: Developers
- Posts: 11,408
- Joined: 23-July 04
- OS:none specified
-
Country:
Posted 24 October 2004 - 08:38 AM
yes,
1) double check your boot.ini
2) use BOOTPART to correct the problem
Recommended tools:
Ranish Partition Manager
http://www.ranish.com/part/
Bootpart
http://www.winimage.com/bootpart.htm
See my post here:
http://www.msfn.org/board/index.php?showtopic=25365&hl=path
jaclaz
1) double check your boot.ini
2) use BOOTPART to correct the problem
Recommended tools:
Ranish Partition Manager
http://www.ranish.com/part/
Bootpart
http://www.winimage.com/bootpart.htm
See my post here:
http://www.msfn.org/board/index.php?showtopic=25365&hl=path
jaclaz
#17
- The Finder
-
- Group: Developers
- Posts: 11,408
- Joined: 23-July 04
- OS:none specified
-
Country:
Posted 24 October 2004 - 08:50 AM
Though seemingly unrelated, here is a list of USB sticks that work on Xbox, if they work there they WILL work on PC, whilst devices reported as NON WORKING on Xbox MIGHT work on PC also:
jaclaz
Quote
1 Devices that do work
3System USB Flash Disk USB Drive 32 MB (1998 blocks)
Aigo 128MB USB Memory Stick (7997 blocks)
Apacer 256Mb USB Key (Paradigit)
AVB 64 MB USB 1.1 Mobile Drive (4030 blocks, ID 0ea0:6803)
Belkin 32MB USB Memory Stick
Captiva USB BAR 128 MB (7989 blocks)
Commodore Floppy -on- stick 128MB (7989 blocks)
COMSOL 16MB
COMSOL 128MB
Creative Labs Nomad Muvo MP3 Player 128MB (7997 blocks)
Dolphin PowerCAM 2.0 Megapixel Digital Camera FASTUSB-1015
Digital Research MP3 player 32MB (~5092 blocks)
Digitrex DSC-1300 camera, in Mass Storage mode (8MB)
EasyDisk 32MB (2014 Blocks)
EasyDisk 128MB (7997 Blocks)
Freecom USB Stick 32 MB (1998 blocks)
Fujitsu Siemens 64MB Menustick
Fujitsu Siemens SB-512 MemoryBird USB-2.0 (512MB, how do I get MechInstaller onto it? - sajb)
Gateway 16MB USB Flash Drive (998 blocks), Windows sees it as "USB NAND FLASH DISK", VID:0c45 PID:1060
Gateway 32MB USB Flash Drive (1998 blocks), Windows sees it as "MFG FLASH DRIVER", Vendor=0c45 ProdID=1060
Hama 6-in-1 USB Card Reader (Model-Nr.: 46958) with Lexar Media 16MB CompactFlash (992 blocks)
HP Photosmart 315 with 8 MB SanDisk CF Card
HP Photosmart C618 Digital Camera
IBM 32 MB USB Memory Key (1998 blocks)
KBGear JamP3 Player (9998 blocks)
KingMax USB2.0 Flash Drive 512MB - KS/PD2-512M (31994 blocks)
Kingston DataTraveler 32 MB (1998 blocks) & 256 MB (15740 blocks)
Lexar JumpDrive Secure 128 MB (7869 blocks)
Lexar JumpDrive Secure 256 MB (15740 blocks)
Lexar JumpDrive Sport 64 MB
Linksys Instant USB Disk 64 MB (Model USBM64M) (3998 blocks)
Logic3 16MB USB (991 blocks)
Medion USB 128 MB (7997 blocks)
Memorex 64 MB (4030 blocks) & 128 MB
Memorex ThumbDrive 256MB (16116 blocks)
Memory in Black USB memory pens from 32 to 512 MB, both the PQI-based and Opti-based models
Micro Advantage 64MB (4008 blocks)
Minolta DiMAGE F300 with 64MB SD-Card
M-Systems DiskOnKey 8MB (486 blocks)
Nikon Coolpix (test with 1x 16 MB and 2x 128 MB CF/SD cards)
Nikon Coolpix 995 w/128MB SanDisk CompactFlash
Ocean 8 MB (490 blocks)
Olympus D-510 Zoom Digital Camera with 64 MB SmartMedia (3990 blocks)
Olympus D-550 Digital Camera with 128 MB SmartMedia (7997 blocks)
Olympus D-380 Digital Camera with 64 MB SmartMedia (MechInstaller - Open 8-32MB image and write to 64MB)
Oti 32 MB
Paradigit 128 MB USB2.0 memory stick (aka Apacer memory stick) (7837 blocks)
PNY 64 MB (3998 blocks)
PQI "Travelling Disk" translucent USB sticks, 64 and 128MB at least
(all 0ea0:6803; some models (09a6:8001) say "damaged", though)
Prolific USB Flash Disk 256 MB (15996 blocks)
SanDisk Cruzer Mini USB Flash Drive 128MB (USB 2.0) Works Great for mechassault install
SanDisk Cruzer Mini USB 128MB - Had to use 8MB-32MB image
Sandisk Mini Cruzer 256Mb USB 2.0 (15k+ blocks - tossed my notes on this)
Samsung 64Mb USB disk (4030 blocks)
Sony 64MB MicroVault (USB 2.0) - 3998 blocks - for MechInstaller, open 8-32MB .img, write to 64MB stick. Has security features, see JetFlash below (?)
Soyo CigarPro2 (USB 2.0, 128MB--the green plastic one) - shows up as "Prolific USB Flash Disk" on WinXP (7997 blocks)
Sweex 128 MB
Transcend JetFlash 64 MB - se below
Transcend JetFlash 128 MB - Depending on model, there are 6 JetFlash types, see link
http://www.transcendusa.com/Products/ModLi...eldNo=2&CatNo=4 and info in the paragraph above.
TwinMos MobileDisk III 64 MB (3998 Blocks)
Twinmos Mobile Disk USB 1.1 Pocket Pen Drive 64B (seller p/n XPD64) (Manuf p/n FMD064S)
(0ea0:6803,Manuf="USB",Prod="Solid state disk")
Typhoon USB Memory Adapter 32 MB (USB 1.1, Art. Nr. 83049, 2014 blocks, for MechInstaller, open
"MechInstaller-1.0-FATX-8MB-to-32MB.img", write to 32MB stick)
Universal Smart Drive 64MB - used 8mb-32mb image
USB UltraDrive 32 MB (1998 blocks)
Zyon Systems 64MB popdrive - commonly handed out to trade show patrons:) - must be plugged in before xbox is powered on, otherwise nothing.
2 Devices that don't work
AIPTEK PenDisk 64MB
Apacer HandyDrive 64 MB (0d7d:0100, not detected)
Atech Pro-9 Card Reader with 8 CF or memory stick (not detected)
Belkin Media Reader USB2 8-in-1 (F5U248) with at least 4 different SM/CF media, from 32 to 128 MB (not detected)
Ben MP3 and Pen Drive 64MB
Casio Qv3000 Camera with with 8 meg casio CF-8x card (makes the screen flash over and over..)
Creative MuVo 128MB
Creative MuVo 64MB
Creative NOMAD MuVo NX 128meg (Xbox said "damaged" but then formatted it with 7005 blocks. but not recognised on reconnect)
Dazzle Memory Stick Reader (04e6:0314, screen flashes and "damaged" shows up when media removed from reader)
DataFab KESD-USBA Reader with Toshiba 16MB SD Memory Card (Memory screen flashes indefinitely)
Dell branded Lexar 16MB
Dell branded Lexar 64MB
DeLock UISDMC1S, 6x Card Reader with 2 slots + ExtreMEmory 256 MB CF-Card ("damaged")
DeLock UISDMC1S, 6x Card Reader with 2 slots + Apacer 64 MB CF-Card ("damaged")
DeLock UISDMC1S, 6x Card Reader with 2 slots + SanDisk 48 MB CF-Card ("damaged")
DeLock UISDMC1S, 6x Card Reader with 2 slots + 32 MB SmartMedia Card ("damaged")
DeLock UISDMC1S, 6x Card Reader with 2 slots + 64 MB SmartMedia Card ("damaged")
Disgo 512MB PRO USB2 (M-Systems DIS20512R) 0x08EC:0x0012, relative of DriveKey, bootable but "damaged"
Disgo 64MB (Damaged, even when low-level formatted)
DiskOnKey 16MB (says "damaged")
DiskOnKey 64MB (says "damaged")
Frontier Labs NexII with 8 meg Casio CF-8x card ("damaged")
FujiFilm FinePix 6800Z Camera (tested with 16 MB and 128 MB SmartMedia cards)
FUJIFILM 128MB USB 2.0 DRIVE (PLUG & PLAY) (says i may have a corrupt memory card)
HP Photosmart 620 with 256MB SanDisk SD memory card (camera says connected to pc, but xbox does not recognize)
HP Photosmart P-1000 with Hitachi 8MB CompactFlash Card
Hama 6-in-1 USB Card Reader (Model-Nr.: 46958) with PQI 128MB CompactFlash
Hama 6-in-1 USB Card Reader (Model-Nr.: 46958) with SanDisk 128MB SecureDigital
Hama 6-in-1 USB Card Reader (Model-Nr.: 46958) with HAMA SmartMedia 32MB
Hama 6-in-1 USB Card Reader (Model-Nr.: 46958) with Sony MSA-128A 128MB
Hama 6-in-1 USB Card Reader (Model-Nr.: 46958) with SanDisk 128MB CompactFlash (says "damaged")
Hama 6-in-1 USB Card Reader (Model-Nr.: 46958) with Canon 8MB CompactFlash (says "damaged")
Imation FlashGo! (IMN-USB-FG1) with at least 4 different SM/CF media, from 32 to 128 MB ("damaged")
Iomega PocketZIP 40 USB (says "damaged")
Iomega ZIP 250 USB (says "damaged" on all media)
Jump Shot 8MB (says "damaged")
KingMax usb 64 (says "damaged")
Kodak EasyShare CX6230 Camera -- neither internal memory nor 256 MB Sandisk SD card -- no apparent recognition by XBOX
Lexar JumpDrive 64MB USB memory stick
Lexar JumpDrive 128MB
Lexar JumpDrive Trio with 128mb Secure Digital card (says "damaged")
LG Flatron USB Drive 64 MB from haansecure (Korea) (says "damaged")
Memorex USB -> CF Card Reader, causes the memory page in the Dash to flicker repeatedly, tried with multiple CF (32, 64, 128)
Mercury Cyberpix - all models (says "damaged")
NAPA P22 WMA mp3 player
No-name (Lexar Chipset + Samsung Memory) 128 Meg USB 2.0 (not detected)
Nikon Coolpix 775 (with 8Mb Nikon card or 32MB Sandisk card) -- no apparent recognition by XBOX
Nikon Coolpix 5400 w/32mb sd card. (shows moving rectangle on camera display and never connects)
Olympus USB SmartMedia Reader-Writer with at least one card of unknown size
Packard Bell AudioKey 32MB
PNY Attache 64MB (says "damaged")
PQI "Travelling Disk" translucent USB sticks, 64 MB (some work, some (09a6:8001) say "damaged")
QDI U2Disk 64MB
SanDisk Cruzer with SD 256MB card.
SanDisk ImageMate combination CompactFlash/SmartMedia to USB adapter
Softick Card Export II (SD drive emulation for the Palm OS - Uses USB mass storage driver) (Xbox breifly recognizes the card 1 time out of 10 - will format in FatX, but will not read savegames - Screen flashes)
Sony Cyber-shot DSC-P31 with Memory Stick (054c:0010, Camera recognizes USB connection but XBox screen flashes)
Sony Cyber-shot DSC-P32 with Memory Stick
Sony Cyber-shot DSC-p71 (makes the screen flash over and over..)
Sony DCR TRV18E Digital Camcorder with Memory Stick
Sony DCR TRV-25 Digital Camcorder with Memo
Sony Micro Vault 256 MB USB 2.0
Topcom Pocket Memory II 256 MB
Transcend JetFlash 2A 128MB (TS128MJF2A, 0c76:0005, see link above) just makes the memory screen flash forever.
3System USB Flash Disk USB Drive 32 MB (1998 blocks)
Aigo 128MB USB Memory Stick (7997 blocks)
Apacer 256Mb USB Key (Paradigit)
AVB 64 MB USB 1.1 Mobile Drive (4030 blocks, ID 0ea0:6803)
Belkin 32MB USB Memory Stick
Captiva USB BAR 128 MB (7989 blocks)
Commodore Floppy -on- stick 128MB (7989 blocks)
COMSOL 16MB
COMSOL 128MB
Creative Labs Nomad Muvo MP3 Player 128MB (7997 blocks)
Dolphin PowerCAM 2.0 Megapixel Digital Camera FASTUSB-1015
Digital Research MP3 player 32MB (~5092 blocks)
Digitrex DSC-1300 camera, in Mass Storage mode (8MB)
EasyDisk 32MB (2014 Blocks)
EasyDisk 128MB (7997 Blocks)
Freecom USB Stick 32 MB (1998 blocks)
Fujitsu Siemens 64MB Menustick
Fujitsu Siemens SB-512 MemoryBird USB-2.0 (512MB, how do I get MechInstaller onto it? - sajb)
Gateway 16MB USB Flash Drive (998 blocks), Windows sees it as "USB NAND FLASH DISK", VID:0c45 PID:1060
Gateway 32MB USB Flash Drive (1998 blocks), Windows sees it as "MFG FLASH DRIVER", Vendor=0c45 ProdID=1060
Hama 6-in-1 USB Card Reader (Model-Nr.: 46958) with Lexar Media 16MB CompactFlash (992 blocks)
HP Photosmart 315 with 8 MB SanDisk CF Card
HP Photosmart C618 Digital Camera
IBM 32 MB USB Memory Key (1998 blocks)
KBGear JamP3 Player (9998 blocks)
KingMax USB2.0 Flash Drive 512MB - KS/PD2-512M (31994 blocks)
Kingston DataTraveler 32 MB (1998 blocks) & 256 MB (15740 blocks)
Lexar JumpDrive Secure 128 MB (7869 blocks)
Lexar JumpDrive Secure 256 MB (15740 blocks)
Lexar JumpDrive Sport 64 MB
Linksys Instant USB Disk 64 MB (Model USBM64M) (3998 blocks)
Logic3 16MB USB (991 blocks)
Medion USB 128 MB (7997 blocks)
Memorex 64 MB (4030 blocks) & 128 MB
Memorex ThumbDrive 256MB (16116 blocks)
Memory in Black USB memory pens from 32 to 512 MB, both the PQI-based and Opti-based models
Micro Advantage 64MB (4008 blocks)
Minolta DiMAGE F300 with 64MB SD-Card
M-Systems DiskOnKey 8MB (486 blocks)
Nikon Coolpix (test with 1x 16 MB and 2x 128 MB CF/SD cards)
Nikon Coolpix 995 w/128MB SanDisk CompactFlash
Ocean 8 MB (490 blocks)
Olympus D-510 Zoom Digital Camera with 64 MB SmartMedia (3990 blocks)
Olympus D-550 Digital Camera with 128 MB SmartMedia (7997 blocks)
Olympus D-380 Digital Camera with 64 MB SmartMedia (MechInstaller - Open 8-32MB image and write to 64MB)
Oti 32 MB
Paradigit 128 MB USB2.0 memory stick (aka Apacer memory stick) (7837 blocks)
PNY 64 MB (3998 blocks)
PQI "Travelling Disk" translucent USB sticks, 64 and 128MB at least
(all 0ea0:6803; some models (09a6:8001) say "damaged", though)
Prolific USB Flash Disk 256 MB (15996 blocks)
SanDisk Cruzer Mini USB Flash Drive 128MB (USB 2.0) Works Great for mechassault install
SanDisk Cruzer Mini USB 128MB - Had to use 8MB-32MB image
Sandisk Mini Cruzer 256Mb USB 2.0 (15k+ blocks - tossed my notes on this)
Samsung 64Mb USB disk (4030 blocks)
Sony 64MB MicroVault (USB 2.0) - 3998 blocks - for MechInstaller, open 8-32MB .img, write to 64MB stick. Has security features, see JetFlash below (?)
Soyo CigarPro2 (USB 2.0, 128MB--the green plastic one) - shows up as "Prolific USB Flash Disk" on WinXP (7997 blocks)
Sweex 128 MB
Transcend JetFlash 64 MB - se below
Transcend JetFlash 128 MB - Depending on model, there are 6 JetFlash types, see link
http://www.transcendusa.com/Products/ModLi...eldNo=2&CatNo=4 and info in the paragraph above.
TwinMos MobileDisk III 64 MB (3998 Blocks)
Twinmos Mobile Disk USB 1.1 Pocket Pen Drive 64B (seller p/n XPD64) (Manuf p/n FMD064S)
(0ea0:6803,Manuf="USB",Prod="Solid state disk")
Typhoon USB Memory Adapter 32 MB (USB 1.1, Art. Nr. 83049, 2014 blocks, for MechInstaller, open
"MechInstaller-1.0-FATX-8MB-to-32MB.img", write to 32MB stick)
Universal Smart Drive 64MB - used 8mb-32mb image
USB UltraDrive 32 MB (1998 blocks)
Zyon Systems 64MB popdrive - commonly handed out to trade show patrons:) - must be plugged in before xbox is powered on, otherwise nothing.
2 Devices that don't work
AIPTEK PenDisk 64MB
Apacer HandyDrive 64 MB (0d7d:0100, not detected)
Atech Pro-9 Card Reader with 8 CF or memory stick (not detected)
Belkin Media Reader USB2 8-in-1 (F5U248) with at least 4 different SM/CF media, from 32 to 128 MB (not detected)
Ben MP3 and Pen Drive 64MB
Casio Qv3000 Camera with with 8 meg casio CF-8x card (makes the screen flash over and over..)
Creative MuVo 128MB
Creative MuVo 64MB
Creative NOMAD MuVo NX 128meg (Xbox said "damaged" but then formatted it with 7005 blocks. but not recognised on reconnect)
Dazzle Memory Stick Reader (04e6:0314, screen flashes and "damaged" shows up when media removed from reader)
DataFab KESD-USBA Reader with Toshiba 16MB SD Memory Card (Memory screen flashes indefinitely)
Dell branded Lexar 16MB
Dell branded Lexar 64MB
DeLock UISDMC1S, 6x Card Reader with 2 slots + ExtreMEmory 256 MB CF-Card ("damaged")
DeLock UISDMC1S, 6x Card Reader with 2 slots + Apacer 64 MB CF-Card ("damaged")
DeLock UISDMC1S, 6x Card Reader with 2 slots + SanDisk 48 MB CF-Card ("damaged")
DeLock UISDMC1S, 6x Card Reader with 2 slots + 32 MB SmartMedia Card ("damaged")
DeLock UISDMC1S, 6x Card Reader with 2 slots + 64 MB SmartMedia Card ("damaged")
Disgo 512MB PRO USB2 (M-Systems DIS20512R) 0x08EC:0x0012, relative of DriveKey, bootable but "damaged"
Disgo 64MB (Damaged, even when low-level formatted)
DiskOnKey 16MB (says "damaged")
DiskOnKey 64MB (says "damaged")
Frontier Labs NexII with 8 meg Casio CF-8x card ("damaged")
FujiFilm FinePix 6800Z Camera (tested with 16 MB and 128 MB SmartMedia cards)
FUJIFILM 128MB USB 2.0 DRIVE (PLUG & PLAY) (says i may have a corrupt memory card)
HP Photosmart 620 with 256MB SanDisk SD memory card (camera says connected to pc, but xbox does not recognize)
HP Photosmart P-1000 with Hitachi 8MB CompactFlash Card
Hama 6-in-1 USB Card Reader (Model-Nr.: 46958) with PQI 128MB CompactFlash
Hama 6-in-1 USB Card Reader (Model-Nr.: 46958) with SanDisk 128MB SecureDigital
Hama 6-in-1 USB Card Reader (Model-Nr.: 46958) with HAMA SmartMedia 32MB
Hama 6-in-1 USB Card Reader (Model-Nr.: 46958) with Sony MSA-128A 128MB
Hama 6-in-1 USB Card Reader (Model-Nr.: 46958) with SanDisk 128MB CompactFlash (says "damaged")
Hama 6-in-1 USB Card Reader (Model-Nr.: 46958) with Canon 8MB CompactFlash (says "damaged")
Imation FlashGo! (IMN-USB-FG1) with at least 4 different SM/CF media, from 32 to 128 MB ("damaged")
Iomega PocketZIP 40 USB (says "damaged")
Iomega ZIP 250 USB (says "damaged" on all media)
Jump Shot 8MB (says "damaged")
KingMax usb 64 (says "damaged")
Kodak EasyShare CX6230 Camera -- neither internal memory nor 256 MB Sandisk SD card -- no apparent recognition by XBOX
Lexar JumpDrive 64MB USB memory stick
Lexar JumpDrive 128MB
Lexar JumpDrive Trio with 128mb Secure Digital card (says "damaged")
LG Flatron USB Drive 64 MB from haansecure (Korea) (says "damaged")
Memorex USB -> CF Card Reader, causes the memory page in the Dash to flicker repeatedly, tried with multiple CF (32, 64, 128)
Mercury Cyberpix - all models (says "damaged")
NAPA P22 WMA mp3 player
No-name (Lexar Chipset + Samsung Memory) 128 Meg USB 2.0 (not detected)
Nikon Coolpix 775 (with 8Mb Nikon card or 32MB Sandisk card) -- no apparent recognition by XBOX
Nikon Coolpix 5400 w/32mb sd card. (shows moving rectangle on camera display and never connects)
Olympus USB SmartMedia Reader-Writer with at least one card of unknown size
Packard Bell AudioKey 32MB
PNY Attache 64MB (says "damaged")
PQI "Travelling Disk" translucent USB sticks, 64 MB (some work, some (09a6:8001) say "damaged")
QDI U2Disk 64MB
SanDisk Cruzer with SD 256MB card.
SanDisk ImageMate combination CompactFlash/SmartMedia to USB adapter
Softick Card Export II (SD drive emulation for the Palm OS - Uses USB mass storage driver) (Xbox breifly recognizes the card 1 time out of 10 - will format in FatX, but will not read savegames - Screen flashes)
Sony Cyber-shot DSC-P31 with Memory Stick (054c:0010, Camera recognizes USB connection but XBox screen flashes)
Sony Cyber-shot DSC-P32 with Memory Stick
Sony Cyber-shot DSC-p71 (makes the screen flash over and over..)
Sony DCR TRV18E Digital Camcorder with Memory Stick
Sony DCR TRV-25 Digital Camcorder with Memo
Sony Micro Vault 256 MB USB 2.0
Topcom Pocket Memory II 256 MB
Transcend JetFlash 2A 128MB (TS128MJF2A, 0c76:0005, see link above) just makes the memory screen flash forever.
jaclaz
#18
Posted 24 October 2004 - 09:47 AM
Ive been trying diffrent methods for getting this to work on my visiontek 1 gig flash drive and I can get dos to boot but not for the life of me will winpe boot, sometimes it hangs, sometimes it gets like cant boot errors. Its very strange im still messing with it. 
#19
Posted 25 October 2004 - 09:23 PM
Well I got it working on my main system here, I havent had the time to try it on other systems yet. I used the simplest method and it actualley worked so suprised. I had been trying alot of diffrent methods and none of them where working except the simpliest hah. So I used the HP tool to format the drive just regular NOT with DOS files. Copied over the windows PE files before an ISO build. and put the ntdetect.exe in the root renamed the setupldr.bin to ntldr and put it in the root also and deleted the other files except the winbom.ini and it boots like a charm. This perticuler bios supports boot from USB HDD, USB Floppy, USB CDROM and USB something else. So it has the compatability, im gonna go ahead and try it on a few of my other systems and let you all know how I fare. But to say the least im pretty stoked.
BTW. I have a VisionTek 1 GB USB 2.0 Flash Drive. Just to let the people that are trying to do this but have not succeeded yet, it is a pretty slow solution even at USB 2.0. It will take a bit to boot but once its up it runs pretty nice. It does have a bit of a lag but its not that bad. Also I was reading for the really hard up folks with no bios support for USB I was reading you could use a floppy disc or even a cdrom really thats bootable to load just the usb drivers and then continue to boot from the USB , but I havent tested that method as it has not applied to my situation yet.
BTW. I have a VisionTek 1 GB USB 2.0 Flash Drive. Just to let the people that are trying to do this but have not succeeded yet, it is a pretty slow solution even at USB 2.0. It will take a bit to boot but once its up it runs pretty nice. It does have a bit of a lag but its not that bad. Also I was reading for the really hard up folks with no bios support for USB I was reading you could use a floppy disc or even a cdrom really thats bootable to load just the usb drivers and then continue to boot from the USB , but I havent tested that method as it has not applied to my situation yet.
#20
- Junior
-
- Group: Members
- Posts: 87
- Joined: 07-June 04
Posted 26 October 2004 - 02:51 AM
What do you mean when you say "HP tool to format the drive just regular NOT with DOS files"?
How regular? NTFS?FAT?
How regular? NTFS?FAT?
