cdob

Windows 98 support UDF and list UDF names. Windows 95 dosn't support UDF and list ISO9660 names. What about nice ISO9660 names at DVD?

Comment all CopyFiles lines. Example [iaStor_Inst] AddReg = iaStor_Temp_parameters_AddReg ;CopyFiles=CopyFullPort FeatureScore=0x80

I'm convinced its a false warning. Feel free to compile setup.c at MinGW too.

Yes, edit file textsetup.sif first. Add files and load the RAM disk driver. 234567 sectors is a example. You have to adjust the example to your needs.In adddisiton: 234567 is not 234,567. Is 234,567 a valid grub4dos number? Read Post #69: MkISO_RAMload_sort.cmd creates a file RAMboot.lst too. This file contain the sector number. Try the menu.lst examples from Post #69.

That's a non default directory. This version is edited by someone. Try a default 2000 SP4 with pre SP5. The dc7100 SFF use a Intel 915 chipset. May be set IDE emulation mode in BIOS.

Did you use winnt32 /tempdrive switch with the /syspart switch?

That's the most importand part at a multi boot CD. Choose filesystems and extensions required by integrated parts. You can easily shoot yourself in the foot. A simple filesystem change may prohibit booting. Yes, Joliet is not required for a windows installation. No, that's false. UDF is not required. Mscdex dosn't read UDF. Installation dosn't use UDF. UDF is a waste of space. Remember you compare a ISO9660 (1988) media with another ISO9660:1999 media. After testing, yes mscedx does read a file at end of a DVD. A media greater 4gb is supported.

Load whole ISO image to RAM. Use grub4dos write to change setupp.ini in RAM. That's another question. There are more different files.Siginet offers a solution already: http://www.msfn.org/board/index.php?showtopic=140351

Well Nero and MagicIso provided a non bootable DVD. I understand the main difference was the burn engine. What about writing the CD image to DVD with ImgBurn? The true reason may be hardware still: burner firmware or media A good burn engine knows burner firmware limitations and provide exceptions for certain firmwares. Another question: Does mscdex support a media greater 4gb ? Well you decline the most reliable ISO build engine. Grub4dos search a file menu.lst. A file menu.lst is not MENU.LST. This is case sensitive at ISO9660 and Rock Ridge. Joliet is not supported. Use either a ISO9660 menu.lst or a Rock Ridge menu.lst. There are three approaches: 1) Use a ISO9660 MENU.LST and a Rock Ridge menu.lst. Mkisofs and MagicIso support Rock Ridge. 2) A file menu.lst is possible within ISO9660:1999. First set appropiate case at hard disk to files and directories. Build a ISO9660:1999 media. MagicIso, Nero and ImgBurn support ISO9660:1999 too. All previous mentioned tools support ISO9660:1999. So does mscdex at given limitations: DOS (upper case) names only 3) Or patch grub4dos: change menu.lst to MENU.LST Then you may use a ISO9660 name MENU.LST. BTW: Win98 can't read a 8.4gb ISO9660 file from DVD. A 8.4gb file is within ISO9660 level 3.

Well, that's the drawback of graphical tools. A user dosn't learn back ground knowledge. The mentioned input was correct.But the file names are hard disk wasn't mentioned. I asssumed upper case names. Don't trust explorer view. The explorer does NOT view direcctory and file names at hard disk.DOS winfile does show direcctory and file names at hard disk. Then there is another reason.Broken burn application was mentioned already. Congratulations.Then it was the burn application. Yes ImgBurn is a very trustworthy application as for burning a image. I'm curious: did you used the Win98 machine and ImgBurn?

First I suspect hardware still. Did you used mixed case ISO9660 names previously? Did you used two independend filesystems? Upper cased ISO9660 names and mixed case Joliet names? As the manpage indicate -iso-level 4 map to ISO9660:1999.ISO9660:1999 allows mixed case ISO9660 names. Mkisofs print a warning if you request a -iso-level 4 file system. Mkisofs preserve case: a upper case name from the OS goes to a upper case ISO9660 name a lower case name from the OS goes to a lower case ISO9660 name The user requested this behaviour by selecting iso-level 4 The OS case names are preserved at iso-level 4. I don't know normal DOS conditions. Which DOS do you use?Win98 command prompt: A directory name "DirectX" goes to "DirectX" at ISO9660 name. The case is preserved. ISO9660 level 3 allows uppercase names only. ISO9660 names are upper cased. It's follow ISO9660 requirements. Feel free to read ISO9660 specification. I don't think so.Mkisofs is a very reliable application. Trash input result to trash output. Good input result to good output. I used a Win98 SE OEM CD. This CD is bootable and joy.sys included already.I extracted files including floppy image and added a 3.7GB file. And installed at VMware Player. Yes, that's a well known Nero bug. Broken burn application, DVD media or writer. A CD image is writable and bootable at DVD. We are back at broken hardware. CMC media are for the trash bin.

Well mscdex does work with "-iso-level 4", as long you use DOS names. That's upper case names. SHSUCDX support lowercase ISO9660 names too. Anyway it's unclear still: hardware or software. Did you read the CD to a image and write a DVD so far? Win98 Jo.sys does work at a floppy emulation 4.29gb DVD. mkisofs -v -D -N -V WIN9XDVD -b floppy.ima -hide floppy.ima -hide boot.catalog -split-output -o WIN9XDVD.ISO D:\temp\WIN98 manpage

Did you add cygwin1.dll, that's the main difference. There are inodes now. Yes, be careful about differences XP SP3 and 2K03. Cygwin inodes support hard links too. I've several XP versions at hard disk, identical files are hard linked. This save considerable space at hard disk. And builded a multi boot cd, files are added once only. There is a readme.sort at source code too. Requirements are strange at first glance, but make sense. ftp://ftp.berlios.de/pub/cdrecord/alpha/ Setupldr.bin and ntldr access first 4gb of media. Textmode boot files and XP asms directory has to be within first 4gb of media. You may specify directories and wildcards.Example, ISO source files are at current directory . ./boot.catalog 10000 ./bootsect 9990 ./WIN* 9978 ./AMD64/* 1100 ./AMD64/SYSTEM32 9000 ./AMD64/COMPDATA 20 ./AMD64/LANG 1000 ./AMD64/WINNTUPG 100 ./I386/* 1100 ./I386/SYSTEM32 9000 ./I386/COMPDATA 20 ./I386/LANG 1000 ./I386/WIN9XMIG 100 ./I386/WIN9XUPG 100 ./I386/WINNTUPG 100 ./DOCS -1000 ./DOTNETFX -1000

In addition there is fake isohybrid with grub4dos. http://www.boot-land.net/forums/index.php?...ost&p=88531

Msys/mingw dosn't provide inodes. Cygwin provide inodes at windows. I'm using a cygwin compiled mkisofs.http://cdrecord.berlios.de/ http://www.student.tugraz.at/thomas.plank/ Trust the newest available version.

If it helps the A/V vendors to solve the matter: integrated file \setup\src\setup.c contain the source code

Can you clarify: what did you do? Did you run 7-zip beta and opened the floppy archiv XP_INST.IMA? Did you extracted any file? Did you run any extracted application? Well, this may be a file system corruption or registry corruption. There may a malvare involved or not. a malvare may be active already, before downloading XP_INST_v04.7z. Hardware failure is another possible cause. What do you suggest instead now?

Did you check the file at virsusscan.jotti.org and virustotal.com?http://www.virustotal.com/analisis/2aca40a...0154-1265529826 Zero scanner reports anything at the image. Which file should contain the wmf exploit? BTW, there is no single wmf included. Reports are taken seriously, but there is no proof so far. The problem is at one machine so far. May be another reason, not the mentioned file.

@LoneCrusader To verify hardware again: read the existing boot CD to a single image file write this image file to a DVD Does the DVD boot?

Broken media or broken writer. Use high quality media. This indicates hardware too. Try another hardware.

There is a driver meiudf.sys. http://panasonic.net/pcc/products/int_driv...9574drv_xp.html

Good idea. However I don't have a answer currently, I'll keep this in memory. Maybe there is a answer in future. Try remove the chipset driverpack. Topic 137714 XP_INST_v04.7z.Attached again: driversigning.c and dsigning.exe. PNP failed, most likely because of signing failed.driversigning.7z

http://support.microsoft.com/kb/889719/

I like this machine, destroyed five years of USB knowledge. So far CriticalDeviceDatabase settings, drivers settings and driver files did work. Time to invent a new approach: early PNP Unfortunately without own testing hardware. Can you do another test? Boot to Shift-F10 prompt and run @echo off setlocal EnableExtensions EnableDelayedExpansion :USB_PNP.cmd :: Batch to load USB devices - XP 32bit :: by cdob v0.01 set Seed=%random%%random%%random% set Seed=0x%Seed:~,8% reg.exe add "HKLM\SYSTEM\WPA\Pnp" /f /t REG_DWORD /v "Seed" /d %Seed% reg.exe query "HKLM\SYSTEM\WPA\Pnp" set Control=HKLM\SYSTEM\CurrentControlSet\Control reg.exe add "%Control%\Session Manager\WPA\Pnp" /f /t REG_DWORD /v "Seed" /d %Seed% reg.exe add "HKLM\SOFTWARE\Microsoft\Driver Signing" /f /t REG_BINARY /v "Policy" /d 00000000 reg.exe add "HKLM\SOFTWARE\Microsoft\Non-Driver Signing" /f /t REG_BINARY /v "Policy" /d 00 reg.exe add "HKLM\Software\Policies\Microsoft\Windows NT\Driver Signing" /f /t REG_DWORD /v "BehaviorOnFailedVerify" /d 0x0 rem set driver signing policy dsigning.exe :: reg.exe add "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup" /f /t REG_DWORD /v "LogLevel" /d 0xFFFFffff rem PNP USB devices and attach drive letter to USB flash drive rem no RunDll32.exe Syssetup.dll,UpdatePnpDeviceDrivers rem devcon.exe [url="http://support.microsoft.com/kb/311272"]http://support.microsoft.com/kb/311272[/url] echo. &echo USB controller and USB HUB for %%a in (PCI\CC_0C0300 PCI\CC_0C0310 PCI\CC_0C0320 USB\ROOT_HUB USB\ROOT_HUB20) do ( devcon.exe hwids "%%a" | find.exe "%%a" && devcon.exe install %SystemRoot%\inf\usbport.inf "%%a" ) echo. &echo USB storage device rem no hwids defined for USB storage device for %%a in (06 05 02 06 05 02) do ( devcon.exe install %SystemRoot%\inf\usbstor.inf "USB\Class_08&SubClass_%%a&Prot_50" ) rem USB keyboard and mouse devcon.exe install %SystemRoot%\inf\usb.inf "USB\COMPOSITE" devcon.exe install %SystemRoot%\inf\input.inf "USB\Class_03" devcon.exe install %SystemRoot%\inf\msmouse.inf "HID_DEVICE_SYSTEM_MOUSE" devcon.exe install %SystemRoot%\inf\keyboard.inf "HID_DEVICE_SYSTEM_KEYBOARD" rem attach drive letter to USB hard disk rem ShowDrive [url="http://bbs.wuyou.com/viewthread.php?tid=116177"]http://bbs.wuyou.com/viewthread.php?tid=116177[/url] ShowDrive.exe rem view drives MountVol.exeaddional applications: dsigning.exe, driversigning part of floppy image http://www.msfn.org/board/index.php?showtopic=137714 devcon.exe http://support.microsoft.com/kb/311272 ShowDrive.exe http://bbs.wuyou.com/viewthread.php?tid=116177

Does exist a file system32\drivers\usbstor.sys at hard disk? Thank's so far. Unfortunately this enhance the confusion, that's more fun USB controller, USB hub and USB storage drivers are loaded.ControlSet001\Enum and ControlSet001\Services seems nice. Maybe a timing problem, BIOS disconnect/reconnect USB at boot. Can you confirm another part? Boot several times to USB, (textmode, first reboot, second reboot, just for fun a third one). Does exist a file reboot.1 and reboot.2 at hard disk? press shift F10 and run reg query hklm\system\currentcontrolset\control\criticaldevicedatabase\USB#CLASS_09Does exist the USB#CLASS_09 entry?