cdob

Or whole previous website http://web.archive.org/web/20071007001559/www.cdshell.org http://web.archive.org/web/20071007001559/www.cdshell.org/download/download.html

i think updating the dummy/empty iso is my problem My crystal ball lost another life. Yes, editing ISO images may truncate names.Thanks for report. Why a fixed list? This match selected "normal" install only. What about a dynamically created list?

"Mkisofs -iso-level 4 -r" allows names up to 193 chars. There is no way this result 8.3 names at DVD.I doubt the new created ISO image is limited to 8.3 chars. Did you create a new ISO image? Yes, above command. No pictures, text only. You may trust my words or not, your choice.Don't you trust the author Bart himself? Why did Bart choose 'mkisofs -iso-level 4' as default for BartPE? Why does long names work at countless machines since 2003? Add verbose output "-v" and post the messages. How do you create the DVD? Do you edit the ISO image after?

Which files are limited to 8characters still?

Get WAIK. Install WAIK. Copy Windows 7 files to a folder c:\XP_7\ Copy Windows XP files to the same folder c:\XP_7\ Adjust boot configuration file c:\XP_7\boot\bcd @ECHO OFF rem edit BCD (boot configuration data) rem add XP \I386\SETUPLDR.BIN to boot DVD set BCD="BCD" BCDedit.exe /store %BCD% /create {ntldr} /d "Install Windows XP" BCDedit.exe /store %BCD% /set {ntldr} device boot BCDedit.exe /store %BCD% /set {ntldr} path \I386\SETUPLDR.BIN BCDedit.exe /store %BCD% /displayorder {ntldr} /addlast Keep resulting ISO file below 4 GB size. oscdimg sorting is almost useless: high cpu load to sort some files, that's insane. dosn't sort folders Oscdimg Command-Line Options Run at c:\XP_7\ oscdimg -n -m -b.\boot\etfsboot.com . \XP_7.iso

Try a manufacturer tool: Creative Suite Enterprise Deployment http://www.adobe.com/devnet/creativesuite/enterprisedeployment.html

Remember plain ISO9660 Level 1 allows 8.3 names only. Hence the current limitation. You have to allow long names to get long names. Bart himself use ISO-9660:1999 http://www.nu2.nu/pebuilder/#intro Try mkisofs -iso-level 4 -r -b grldr -no-emul-boot -boot-load-size 4 -o grldr.iso iso_rootFile case is used from readed files at hard disk. This assumes uppercase core boot file names at hard disk. PEBuilder uppercase reqiured files, if you build a ISO image. Or use mkisofs -iso-level 4 -force-uppercase -r -b grldr -no-emul-boot -boot-load-size 4 -o grldr.iso iso_rootAll ISO9660 names are uppercased at CD.

That's not possible within winnt.sif. Setupdd.sys does detect winnt.sif [unattended] section and use unatended mode. This disables repair option. The unicode string 'unattended' before 'Files.InRepairDirectory' is used at a boot CD. Windows repair dosn't support copy $OEM$ files. That's not a repair anymore. You have to find a work around.

There neither a 8 character limit at BartPE nor at grub4dos. How do you build the ISO image? Change your ISO creating tool settings to create long file names.

Yes. To verfify run 7zip gui and open nvdrsdb.bi_. Read name. No, don't do that.First uncompress the file nvdrsdb.bi_. This result a file nvdrsdb. Next "rename nvdrsdb nvdrsdb.bin". Yes, that's it. The funny reason is a funny nvidia driver hacker.

It's about compression and file names.I'm confused: Post #4 Post #15 There are two different file names. How come? Which file name did you running dism?

I don't understand clearly. Which OemPreinstall feature do you request? Driver part OemFilesPath or another settings? Can you name some examples? Idea: create a multi boot cd. Use different setupldr.bin. Hexedit second setupldr.bin: change winnt.sif to win01.sif. or unattended to __attended

Compressed file nvdrsdb.bi_ contains file nvdrsdb. That's not nvdrsdb.bin. nv4_disp.inf Try integrate compressed files: nvdrsdb.bi_ Or if you prefer expanded files: rename nvdrsdb nvdrsdb.bin

This should be possible.CC_0106 refers to AHCI mode. CC_0104 refers to RAID mode. [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1002&cc_0104]That's one line. Yes, add RAID drivers to BartPE. Integrated help files describe requirements. Or ask at http://www.911cd.net/forums//index.php?showforum=30 There is another aproach.Read your motherboard manual. Attach current system hard disk to Port 4 or Port 5. Goto BIOS. Set RAID mode, but IDE emulation for Port4/5. Boot XP, system is at IDE mode still. And RAID controller is available. install RAID driver. Clone system to 250GB. Connect 2x 74GB to Port 1 and Port 2. Build RAID. Boot 250GB hard disk. Clone system to RAID.

That's the importand part. That's the less importand part.Hard disk is available using windows drivers. But BIOS level boot device is unclear. You may copy files to hard disk, but first boot from hard disk may work or fail. No, it's not if you boot from hard disk. Reason is unclear. If you boot from hard disk with inserted USB drive:Registry settings are changed and another reboot is added. USB drivers are loaded early, this is required at some broken BIOS. A debug setup_dbg.exe is included at floppy image too. Rename / replace file to setup.exe. Setup.cmd messages are displayed on screen now. XP ISO file mounting is at this level. Previous boot failare are another reason. Added: Which USB device do you use? Can you try another USB device? Any USB legacy options at BIOS? Try change legacy settings.

It dosn't work as for a XP installation. As you indicated: hd1 - does not appear What happens to internal hard disk? That's a unpredictable situation. XP setup may add boot code to internal hard disk or another device. Version 5.0.11 is the good version as for a XP installation. Ask the author, if this version fail at given hardware. ISO file was not mounted. May be another BIOS issue.Open floppy image, edit txtsetup.oem and unomment fixBoot.USB line

Yes, make it so.

Windows installation add boot code to (hd0). This may be a remapped device. BIOS, grub4dos and PloP map devices. Which PloP version do you use? PloP device mapping was changed recently. Which grub4dos verson do you use? Boot grub4dos, press c to get command line. Find current mapped drives and verify size 'find (' and tab geometry (hd0) Which devices does exist? Which goes to internal hard disk and which to USB drive? Run PloP and repeat this again. Do you use a winnt.sif file? Does winnt.sif file contain a section [MassStorageDrivers] ? Did textmode setup comlete so far? Yes, boot to hard disk after first boot. How long does reboot takes? Several minutes?Seems to be another unknown BIOS issue. I'm used to USB drive plugged in and reboot from hard disk after textmode. Which message do you get?

This leads to question: Given a superfloppy image: How to create a hard disk image? Let's investigate further. I haven't found a reliable zip disk example, relating MBR and partition boot code. Relating previous links, confusing examples are possible. manufacturer formated zip disk, reading changed by firmware one disk with a MBR, SCSI zip drive read a hard disk and a ATAPI drive read a superfloppy Without real hardware access, I'll ignore zip disk so far. As for a superfloppy image LS120. There are manufacturer hints 240_dd.exe http://panasonic.co.jp/phc/support/oem/lkm/dl.html ftp://ftp.ctxeurope.com/drivers/notebook/2300p/ls120/nt40/fmtdata.ini fmtdata.ini DataFile uhddata.bin contains a MSDOS boot sector image:Sectors per track: 32 Number of heads: 8 Large sectors: 246528 Media type: 0xF0 Hidden sectors: 0x00 Disk number: 0x00 System ID: FAT16 Large sectors, hidden sectors, media type and disk number indicates a superfloppy image too. How to convert a given floppy image to a hard disk image? One appraoch: create a MBR and insert floppy image at LBA 32 Preparations: Create a file ls120.ima 126222336 bytes, dd file uhddata.bin Mount ls120.ima, copy dos files, unmount Testing superfloppy image usingt grub4dos menu.lst title LS120 map /ls120.ima (fd0) map --hook root (fd0) chainloader +1DOS does boot. Include this superfloppy image to a hard disk image. One cylinder is added. MBR boot code used from syslinux mbr.bin. That's 440 bytes. Create a empty file 15944.dat size 15944 bytes. copy /b mbr.bin+15944.dat+ls120.ima ls120.dsk Set partition table 1 : MBR offset 0x1BE to 0x1CD 80 01 01 00 0E 07 E0 C3 20 00 00 00 E0 C3 03 00 Set magic bytes 55 AA at MBR offset 0x1FE to 0x1FF Try hard disk image at QEMU qemu.exe -L . -m 128 -boot c -hda LS120.dsk -hdachs 964,8,32Booting fails, partition error Next partition boot sector changed:Set offset 0x15 to 0xF8 Set offset 0x1C to 0x20 Set offset 0x24 to 0x80 DOS 7 does boot. Add this hard disk image to a El Torito hard disk emulation CD. DOS 7 does boot.

Use a current VMware Player.Create a new or edit a existing virtual machine. At CD/DVD drive select: 'Use ISO Image file', select the file

Why do you like to add files to i386 folder? Do you like to use files at windows installation? There is no general answer. There are different cases. Which kind of files do you like to add? A driver, a application or another one? A mass storage drivers example: And read MSFN Forum Rules 1.a again http://www.msfn.org/board/topic/18408-forum-rules-updated-must-read/

This turns a zip disk to a non zip disk. I understand reference:There is one 100 MB zip disk. (250 MB ignored so far) The same disk can be read different, the read drive makes the difference. Let's investigate: Given a hard disk zip100.vmdk El Torito hard disk emulation and VMWare Player 3: fourth partition table entry used, first blank: Booting fails. black screen, fixed cursor at upper left corner equal first and fourth partition table entry: Booting fails. MBR error message: Multiple active partitions first and fourth partition table entry used, only first active: Dos 7 does boot. first partition table entry used, fourth blank Dos 7 does boot. El Torito Floppy boot: The same ISO file used. Hard disk image starts at DVD LBA 18. 32 hard disk sectors refers to 8 DVD sectors. Hence partition starts at DVD LBA 26. Boot catalog changed to 2.88 floppy and LBA adjusted: 88 04 00 00 00 00 01 00 12 88 03 00 00 00 00 01 00 1A Booting fails, error message from partition boot code: A 2.88 floppy geometry dosn't match a zip geometry.

Can you post a working IBB example: different folders with optimisation? Do you have to adjust file or folder at hard disk in addition?

Not windows cluster size. Internal hard disk sector size. Hardware, not software. Allmost all DOS/Windows compatible hard disk use 512 bytes. However there are some exception nowadays. S2 production date seems to be importand. http://gbatemp.net/t203341-samsung-s2-portable-cfg-usb-loader?pid=2582508&st=0entry2582508 Try a updated grub4dos as recommended first.

Possible cause: BIOS, fixed versus removable drive, USB drive itself Which desktop PC do you use? Did you use the same desktop PC at both? Which Samsung S2 do you use? HX-MU050DA, HX-MU050DC, HX-MTA50DA or another? Does your S2 use 512 byte, 1 kb or 4 kb sectors?