cdob

BSOD 0x7b may relate to the broken SSD too. Can you remove the broken hardware? Can you disable the SSD disk at BIOS? XP does support install from a USB CD-ROM. A default XP SP3 should do this. No BSOD 0x7b so far. There are USB adjustments required for first restart. NTDETECT.COM case is importand at CD.

XP dosn't support your approach by default. USB drivers are not loaded, hence the BSOD 0x7b. Change the drive load order. Dietmar described the behaviour and solution: http://www.911cd.net/forums//index.php?showtopic=14181 There are two projects http://www.ngine.de/index.jsp?pageid=4176 http://www.usboot.org/tiki-index.php

The new batch is called MkMigratgeInf_b.cmd. Sorry for the confusion. I wrote the batch MkMigratgeInf.cmd. As far as I remember you or wimb adjusted this and used the name MkMigrateInf2.cmd in the past. Hence my new file name is MkMigratgeInf_b.cmd. @kisivotinh MkMigratgeInf_b.cmd support one special case in addition: the running windows did use a strange HardwareId. Reasons are unknwon so far. If your condition match this, then MkMigratgeInf_b.cmd solve this. And crossing fixed drive to removable drive or vice versa: drive letter pre assignment fails. There maybe other reasons. I've no further idea currently.

As for: Boot sector file name: bootsect.bin. Boot sector file beside win51* tag files. Get new binaries. Add cygwin1.dll and addional dlls. http://www.student.tugraz.at/thomas.plank/ Copy mkISO_NT_sort.cmd to the same directory. The sort list is created dynamically: Txtsetup.sif is parsed. Textmode boot files are sorted first. Sort order is more or less as setup read the files. DVD drive makes shorter track seek, the file acess time is reduced, Hence the installation part is faster. NT based boot CD are supported like NT4,2000,XP,2003; 32bit and 64bit You may add files greater 4GB. Use a directory for big files. Ntdetect.com dislike big files in root. Usage example: If your XP source files D:\XP_DVD, then run mkiso_NT_sort.cmd D:\XP_DVD mkISO_NT_sort.zip

Describe not bootable: Can you boot DVD at all? Do you get a error message? Which error message do you get? Can you define your conditions? Which XP do you use? Do you use a 32 bit or 64 bit XP? Which layout do you use at DVD? Which directories exist? Why do you need a dual layer DVD? Do you use a multi boot solution? Do you add a lot of files? Do you like to add a big file? A file greater than 4GB. Do you use XP default boot sector? Which boot sector file do you use? Do you use a multi boot loader? like isolinux, grub4dos ... Do you use winnt.sif [MassStorageDrivers] ? A NT like boot CD use file system ISO9660. Do you add non windows files? Do you require a addional extenstion or file system? There are different solutions for different conditions.

Again, not tested so far. Vista / Windows 7 textmode boot directories and files are: boot sector \bootmgr \boot\ \efi\ \sources\boot.wim This should be within first 4GB of media. Does anybody use 'oscdimg -yo' ? http://technet.microsoft.com/en-us/library/dd799243.aspx bootmgr is not listed. The boot sector use BIOS to seek this file. Hence a friendly BIOS is expected, some BIOS may fail. It maybe nice to add bootmgr too. By the way: There is no file size limit at ISO9660:1988. A file can exist of several sections, each below 4GB. The OS concat single sections to one file. Old NT4 does list a PB file at ISO9660:1988. UDF supports medium sized files. WAIK oscdimg.exe does support UDF files greater 4GB, but ISO9660 files below 4GB.

Had to try myself: I created a 7GB ISO file. Windows files are sorted with 'mkisofs -sort' at front of media. All windows files are within first 4GB of media. Burned to DVD+DL at max speed: 2.4 It's a old DVD writer. Booting from DVD is possible. Windows XP does install without errors. After installation, whole DVD is acessable. Yes, a Bootable XP DVD above 4.7GB is possible.

CDmage does work at a DVD image, however DVD are not supported. There are is a nice view: Type, Date and time and Timezone. There are some minor drawbacks. The meter limtit goes up to 80 minutes. Big files show false sizes: file size modulo 4GB LBA are listed. File system ISO9660 is listed, no rock ridge extension or other file systems. As for a bootable XP DVD: Yes, CDmage is compatible. Thanks for the reminder. IsoBuster Free does list rock ridge extension and big files, e.g. 8GB. IsoBuster fails at insane huge files: a 3PB file at ISO9660. http://www.isobuster.com/license-models.php

Well, which data layout do you use? Do you create a multi boot DVD? Do you create a single boot DVD? Do you add big apps? Which foldernames goes apps? Can you change the names? Which foldernames are at DVD? Can you make a 'dir /ad /s /b' Some tools add files by alphabetical sorting order. Hence use folder name \zzz_apps\ for your applications. \zzz_apps\ goes to end of DVD media. Cdimage does use folder deep. A deep folder goes to end of media. Unfortunaltely ASMS folder use deep folders already. This goes to end of media. Hence this may break first boot. Try a ridicilous deep folder \1\2\3\4\5\6\7\8\9\apps\. Not tested. A previous message http://www.msfn.org/board/index.php?s=&amp...st&p=769284

Well, which data layout do you use? Do you create a multi boot DVD? Do you create a single boot DVD? Do you add big apps? Which foldernames goes apps? Can you change the names? Which foldernames are at DVD? Can you make a 'dir /ad /s /b' Some tools add files by alphabetical sorting order. Hence use folder name \zzz_apps\ for your applications. \zzz_apps\ goes to end of DVD media. Cdimage does use folder deep. A deep folder goes to end of media. Unfortunaltely ASMS folder use deep folders already. This goes to end of media. Hence this may break first boot. Try a ridicilous deep folder \1\2\3\4\5\6\7\8\9\apps\. Not tested. A previous message http://www.msfn.org/board/index.php?s=&amp...st&p=769284

Well, I don't have dual layer DVD RW. I avoid testings at dual layer DVD R media so far. I installed XP from a 8 GB image at a virtual machine. Some hints: Cdimage can sort files at directory level. Be careful directoy ASMS may get at end of media. Mkisofs can sort files at file level. Directories and single files can be sorted. As wrote already: IsoBuster list LBA addressed. You may read LBA adresses before burning media. ImgBurn does sort files. And you may set the layer break yourself.

A SATA driver relating to your mass storage CONTROLLER. Should be a ICH7-M. You don't need to add a driver for your hard disk. http://www.msfn.org/board/index.php?showtopic=107504

I haven't done a dual layer DVD bootable XP so far. There is a limitation within 4.7GB already. Maybe this explains dual layer experience too. The file location is importand. ISOBuster list LBA Logical Block Address of files. Setupldr.bin acces first 4 gb of a DVD only. That's textmode boot files has to be within first 4GB of media. Gui mode boot files can be after 4GB boundary. At first reboot there is a similar reason. ASMS files are read from DVD. These files has to be within first 4GB of media too. Later readed files can be after 4GB boundary.

Yes, there is a difference. The BIOS has to use USB code at a USB device. Do you use some kind of U3 sick? Did you integrate the ISO image? This are two different items. There is a difference between a real external optical drive and a fake external optical drive. You may get different results. In addition: can you boot from second partition at USB memorystick?

There are file names used at boot. Try to rename file:Extract Vista boot sector, rename the file. replace the XP boot sector file copy i386\setupldr.bin to \BOOTMGR Actually I've no idea, because there is USB booting involved. Testing would be nice.

Yes, local boot.ini dosn't match. Read FAQ3http://www.msfn.org/board/index.php?showtopic=116766

Most likely. USB install dosn't cause this.

There are a lot of desktops arround \??\STORAGE#RemovableMedia#7&157ad62&0&RM#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b} \??\STORAGE#RemovableMedia#7&141a0a73&0&RM#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b} That's two different USB devices: 7&157ad62&0 and 7&141a0a73&0 Did you mix tow USB devices? Attach the proper USB stick first. Yes, that's a hex values of the string.Use Tiny Hexer, insert text. Compare http://www.msfn.org/board/index.php?s=&amp...st&p=738009

No, don't run this at the desktop. Run this at the nice testing machine: the notebook. Remember the machine produced ParentIdPrefix Or The new batch should convert this settings to 7&141a0a73&0 and 7&207c63a1&0. Use the previous command as jaclaz pointed. Or copy MkMigratgeInf_b.cmd to the USB stick and run MkMigratgeInf_b.cmd direct.

Keep this nice testing machine. Don't remove settings. There is a new MkMigratgeInf_b.cmd attached. Try this version. This version use a pattern RemovableMedia#7&*&0 7 and 0 are fixed, if there another values. Version outdated, removed. Update at http://www.msfn.org/board/index.php?s=&amp...st&p=880257

Thanks for testing. A working windows may use: RemovableMedia#7&*&0 (that's the default) RemovableMedia#7&*&1 RemovableMedia#8&*&0 RemovableMedia#8&*&1 and so on jaclaz found usbhistory. http://nabiy.sdf1.org/index.php?work=usbHistory That's nice. Site mention this too This may store previous settings.@pipster Can you delete above entries? Remove and attach USB stick again. To summerize a idea: A new installed windows use RemovableMedia#7&*&0. This pattern should go to migrate.inf.

At first glance USB serial stick dosn't cause the behaviour. Maybe there is another windows setting? Does windows install files contain a ignore USB serial setting. Hence new installed windows ignore MountedDevices? migrate_XPproSp3.inf \??\STORAGE#RemovableMedia#8&141a0a73&0&RM#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b} migrate_Win2003.inf \??\STORAGE#RemovableMedia#8&157ad62&0&RM#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b} RemovableMedia#8 is very seldom used. Does this relate to hardware or windows? If you boot windows at another machine, does windows use RemovableMedia#7 or RemovableMedia#8 for the USB stick? @pipster Can you install windows again? Which MountedDevices goes to USB stick at new installed windows? If new installed windows use RemovableMedia#7 then a adjusted migrate.inf should work. @jaclaz Uwe offers DriveCleanup to remove USB devices from registry. http://www.uwe-sieber.de/drivetools_e.html

Story reminds to: some HP BIOS dislike grub4dos MBR. http://www.911cd.net/forums//index.php?sho...mp;#entry154745 Do you use a grub4dos MBR?

Does anyone have a fine MountedDevices explanation? How does windows build RemovableMedia string? Lets investigate: MountedDevices value contains at XP machine RemovableMedia: H: \??\STORAGE#RemovableMedia#8&141a0a73&0&RM#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b} I: \??\STORAGE#RemovableMedia#9&1d9465bd&0&RM#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b} J: \??\STORAGE#RemovableMedia#8&207c63a1&0&RM#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b} K: \??\STORAGE#RemovableMedia#9&25791fbe&0&RM#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b} L: \??\STORAGE#RemovableMedia#9&1fde2770&0&RM#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b} I'm used to RemovableMedia#7. There is a example http://www.forensicswiki.org/wiki/USB_History_Viewing RemovableMedia#8 and RemovableMedia#9 is strange. Does a notebook multi-card cause this? Another idea: USB serial number may cause this. Windows does use USB serial number. The USB hardware or a windows setting maybe involved. Read section 'USB serial number' http://www.uwe-sieber.de/usbtrouble_e.html @pipster Does your hardware use a USB serial number? USBDeview http://www.nirsoft.net/utils/usb_devices_view.html UWe does offer a tool too. What about your setting HKLM\SYSTEM\CurrentControlSet\Control\UsbFlags\GlobalDisableSerNumGen ? Did you made a windows full install? Which MountedDevices goes to USB stick at new installed windows?

Warez is not supported here. http://www.msfn.org/board/index.php?showtopic=18408