Jump to content

Windows XP Pro Boot CD (slipstreaming)


Recommended Posts

Posted

Hi,

 

The last day I've tried to generate a slipstreamed XP Pro (SP2) boot CD without success. Now I simply want to create a non-slipstreamed XP Pro boot CD, but still without success.

 

I have the original boot CD, now stored as X1APOEM_DE.ISO on my disk (568.723.456bytes). Using ImgBurn 2.4.0.0 or Altap Salamander 2.5 I've extracted the 2048byte boot image. From the original iso I've extracted all files into an empty directory "H:\XPSETUP". Then I've switched ImgBurn to Build mode, added the directory "H:\XPSETUP\". On the Options card, "ISO9660" is selected and only the checkboxes "Recurse Subdirectories", "Include Hidden Files" and "Include System Files" are selected. On the Labels card, "X1APOEM_DE" without quotes is added in the ISO9660 input field. On the Advanced/Restrictions/ISO9660 card the option "Level X - 219 Characters", "ASCII" and all checkboxes ("Allow More Than 8 Directory Levels", "Allow More Than 255 Characters In Path", "Allow Files Without Extension" and "Don't Add ';' Version Number To Files") are selected. On Advanced/Bootable Disk card the checkbox "Make Image Bootable" is selected, Emulation Type is set to "None (Custom)", Boot Image is pointing to "H:\xp\s01-bootdisk-noemul.img" without quotes, Developer ID is empty, Load Segment is unchanged at 07C0 and Sectors To Load is changed to 4. As build destination h:\xp.iso is chosen.

 

When I click the Build button, I'm asked whether the 'XPSETUP' folder is the root directory for the image and I choose Yes. After a while ImgBurn shows a confirmation dialog with the calculated sizes and I click OK. A few moments later I'm getting the "Operation Successfully Completed!" message, but the generated file h:\xp.iso is larger (572.260.352bytes) than the original image's size (568.723.456bytes).

 

Now I open a virtual machine in Microsoft Virtual PC 2007, click "CD|Capture ISO Image" choosing h:\xp.iso and reboot. On the message "Drücken Sie eine beliebige Taste, um von der CD zu starten ..." I press the space bar and one second later Virtual PC 2007 reboots. Capturing the original iso image X1APOEM_DE.ISO works fine in Virtual PC 2007.

 

I've also tried to add the Joliet file system, too, but the result is the same.

 

Does anybody successfully created a Windows boot CD using ImgBurn 2.4.0.0?

 

Thanks in advance,

Mike

 

ibb file:

IBB

[sTART_BACKUP_OPTIONS]
BuildMode=2
Destination=h:\xp.iso
FileSystem=0
UDFRevision=0
PreserveFullPathnames=0
RecurseSubdirectories=1
IncludeHiddenFiles=1
IncludeSystemFiles=1
IncludeArchiveFilesOnly=0
AddToWriteQueueWhenDone=0
ClearArchiveAttribute=0
VolumeLabel_ISO9660=X1APOEM_DE
VolumeLabel_Joliet=
VolumeLabel_UDF=
Identifier_System=
Identifier_VolumeSet=
Identifier_Publisher=
Identifier_Preparer=
Identifier_Application=
Dates_FolderFileType=0
Restrictions_ISO9660_InterchangeLevel=2
Restrictions_ISO9660_CharacterSet=2
Restrictions_ISO9660_AllowMoreThan8DirectoryLevels=1
Restrictions_ISO9660_AllowMoreThan255CharactersInPath=1
Restrictions_ISO9660_AllowFilesWithoutExtensions=1
Restrictions_ISO9660_DontAddVersionNumberToFiles=1
Restrictions_Joliet_InterchangeLevel=1
Restrictions_Joliet_AllowFilesWithoutExtensions=1
Restrictions_Joliet_AddVersionNumberToFiles=0
Restrictions_UDF_DisableUnicodeSupport=0
Restrictions_UDF_DVDVideoAllowUnicodeVolumeLabel=0
BootableDisc_MakeImageBootable=1
BootableDisc_MediaEmulationType=0
BootableDisc_BootImageFile=H:\xp\s01-bootdisk-noemul.img
BootableDisc_DeveloperIdentifier=
BootableDisc_LoadSegment=07C0
BootableDisc_LoadSectorCount=4
[END_BACKUP_OPTIONS]

[sTART_BACKUP_LIST]
H:\XPSETUP\
[END_BACKUP_LIST]

 

log

; //****************************************\\
;   ImgBurn Version 2.4.0.0 - Log
;   Sonntag, 17 Februar 2008, 10:45:00
; \\****************************************//
;
;
I 10:42:48 ImgBurn Version 2.4.0.0 started!
I 10:42:48 Microsoft Windows Vista Business Edition (6.0, Build 6000)
I 10:42:48 Total Physical Memory: 3.134.848 KB  -  Available: 1.557.944 KB
I 10:42:48 Initialising SPTI...
I 10:42:48 Searching for SCSI / ATAPI devices...
I 10:42:48 Found 1 DVD±RW/RAM!
I 10:42:55 Project Loaded Successfully!
I 10:42:55 File Name: C:\Users\tom\AppData\Roaming\ImgBurn\IBB Files\xppsp2.ibb
I 10:43:12 Operation Started!
I 10:43:12 Building Image Tree...
I 10:43:17 Calculating Totals...
I 10:43:17 Preparing Image...
I 10:43:28 Contents: 6.615 Files, 147 Folders
I 10:43:28 Size: 564.578.186 bytes
I 10:43:28 Sectors: 279.100
I 10:43:28 Image Size: 572.260.352 bytes
I 10:43:28 Image Sectors: 279.424
I 10:44:05 Operation Successfully Completed! - Duration: 00:00:52
I 10:44:05 Operation Started!
I 10:44:05 Image Contents: 6.615 Files, 147 Folders
I 10:44:05 Image Sectors: 279.424
I 10:44:05 Image Size: 572.260.352 bytes
I 10:44:05 Image Single Layer Profile: DVD-R/RW (Media Capacity: 2.298.496)
I 10:44:05 Image Volume Identifier: X1APOEM_DE
I 10:44:05 Image Volume Set Identifier: UNDEFINED
I 10:44:05 Image Application Identifier: IMGBURN V2.4.0.0 - THE ULTIMATE IMAGE BURNER!
I 10:44:05 Image File System(s): ISO9660 (Bootable)
I 10:44:05 Destination File: h:\xp.iso
I 10:44:05 Destination Free Space: 39.790.149.632 bytes (38.857.568 KB) (37.946 MB) (37 GB)
I 10:44:05 Destination File System: NTFS
I 10:44:05 File Splitting: Auto
I 10:44:07 Writing Image...
I 10:44:57 Image MD5: 6f4ddcdc18a6ac0e53ab72489b060e57
I 10:44:57 Operation Successfully Completed! - Duration: 00:00:51
I 10:44:57 Average Write Rate: 10.957 KB/s (73.0x) - Maximum Write Rate: 22.291 KB/s (148.6x)
I 10:45:00 Close Request Acknowledged
I 10:45:00 Closing Down...
I 10:45:00 Shutting down SPTI...
I 10:45:00 ImgBurn closed!

Posted

Are you sure the boot block is only 2k? The one I did the other day was 16 sectors, not 4.

 

You need to look in the log to see that info when you extract it from the original.

Posted (edited)

Hi.

I have the same problem. When I use one ibb project in ImgBurn v2.3.2.0, the bootable iso of wxp pro x64 sp2 is fully functional but the same ibb project in ImgBurn v2.4.0.0 is not functional. :(

Edited by Muki
Posted

It's ok now, I found the problem and fixed it.

 

It seems the 'wide' (unicode) version of the compare function puts filenames starting with '_' before those starting with normal 'A-Z'. This is actually wrong as '_' comes after uppercase letters in the ASCII character set.

 

For that reason, the I386 folder will not be parsed correctly by the installer and hence it just reboots.

 

(The I386 folder contains a file called '_DEFAULT.PI_')

 

You'll have to hold out until 2.4.1.0 is released which I'm sure will happen within the next 7 days.

 

Sorry and thank you for reporting the issue and getting me to look into it properly. :)

Posted
It's ok now, I found the problem and fixed it.

 

It seems the 'wide' (unicode) version of the compare function puts filenames starting with '_' before those starting with normal 'A-Z'. This is actually wrong as '_' comes after uppercase letters in the ASCII character set.

 

For that reason, the I386 folder will not be parsed correctly by the installer and hence it just reboots.

 

(The I386 folder contains a file called '_DEFAULT.PI_')

 

You'll have to hold out until 2.4.1.0 is released which I'm sure will happen within the next 7 days.

 

Sorry and thank you for reporting the issue and getting me to look into it properly. :)

 

Thank you for your quick response and your work on this super program. I am looking forward to next version. :thumbup:

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.