Frontpage
Forums
Tutorials
Members
Calendar
Subscription
Donate
Links
Contact 
Help
I'm stuck right now. I'm trying to include a highly customized unattended XPSP2 install that I created months ago with nLite. I don't have a winnt32.exe file in my i386 folder. How do I get the boot files?
[How To] Multi-boot DVD Guide
Updated and with cool features
Rate Topic:
Back to top
#87
- Amoguai
-
- Group: Members
- Posts: 196
- Joined: 25-November 05
- OS:Windows 7 x64
-
Country:
Posted 05 June 2007 - 03:48 PM
Hi tknaught 
Well, i suppose you have the original Windows Source, so you just need use the SFX geitonaki built (Automatically create multi-boot folders and files (thanks to geitonaki)) and extract the needed files from original source.
You have another option though, create a copy of your files on the hard drive, press Start -> Run -> Browse to Winnt32.exe and add the "/noreboot" command, somethinglike this: "C:\source\Winnt32.exe /noreboot".
Use what suits you better, good luck
André Casal
Well, i suppose you have the original Windows Source, so you just need use the SFX geitonaki built (Automatically create multi-boot folders and files (thanks to geitonaki)) and extract the needed files from original source.
You have another option though, create a copy of your files on the hard drive, press Start -> Run -> Browse to Winnt32.exe and add the "/noreboot" command, somethinglike this: "C:\source\Winnt32.exe /noreboot".
Use what suits you better, good luck
André Casal
#88
Posted 07 June 2007 - 12:54 AM
Ok. First of all. Absolutely, total kick-butt guide. The best I've found. I've been fighting with Powerpacker & am happy to have found a way to make my cd manually.
However, I have an issue w/ DriverPacks currently.
First, my setup:
There's XP PRO VOL, XP PRO OEM, XP Home OEM, and XP Home RTL.
THere's different folders for the 5 different XP VOL Keys we have.
All of which have been integrated w/ RVM, and have some other packs applied, and are working swimmingly.
As you can tell from the screenshot, my current configuration includes and $OEM$ and OEM folder in each /Setup/XP/<folder>
These are the RVM packs everything was build from. Since the $OEM$ is exactly the same for all folders, CDImage is nice enough to save me a ton of space.
However, I don't know if that's the correct approach.....although I've verified it works.
More importantly, though, Driver Packs is NOT working, and I'm trying to figure out why.
Currently, the XP Source folders all have driver packs applied individually......and obviously work that way, as a single install CD.
However, when I put them in the multiboot, we're hosed
I don't know exactly how driver packs work yet, but I know there's a presetup.cmd, I just don't know how it's called.
From what I can tell currently, the only thing changed with the multiboot approach is that the TXTSETUP.SIF has one line changed
And although presetup.cmd is in the file, there is obviously something amuck w/ the current use of my OEM folder (automatically created by driver packs)
So, my questions are as follows:
#1. What is the most correct approach for the $OEM$ folder? One per setup source underneath the /Setup directory, or is there a better method
#2. Aside from trying driver packs w/ the multiboot approach, which is my next test, is there a way to make my current driver pack setup work properly?
And again, this thread kicks major butt. Thanks a ton.
My next step once I fix driver packs is to add on a slipstreamed 2K3 (Ent, Std, Web),and finally, a custom XPE (think Sherpya) buld I already have.
FYI, I did not have a need for using the install.cmd/<youros>.tag method because my apps are integrated already via SVCPack, regedts are imported via commands.txt and then I use WPI after installation.
Thanks for any reply.
Calpha.
PS. The create folders batch file blew my **** mind....looking at the source. And I'm a developer. I was totally impressed with the tricks applied in changing the file contents and never would have thought in a million years to do it........although admittedly, I don't understand the code exactly.......but am trying.
PSS. I will update when I try method 2 (multiboot apprach) with applying the driver packs.
Update: Driver Packs Working
I missed two things.
#1. Do Driver Packs Last. I was running the create_folders_.cmd on my Sources and then doing the driver packs. DOH!
#2. Bashrat's directions work perfectly for multiboot: I flummoxed the last try somehow, but they're working now.
Here's more clarification:
I have 6 Versions of XP currently.
These folders all exist at c:\dvd\setup\xp\
XP-VLK (RVM UpdatePack, 20+ Addons)
XP-VLK-MINI (RVM UpdatePack IE7, WMP11)
XP-OEM (RVM UpdatePack, 20+ Addons)
XP-OEM-MINI (RVM UpdatePack IE7, WMP11)
XPHomeOEM ( UpdatePack, 20+ Addons)
XPHomeRTL (UpdatePack, 20+ Addons)
From there, XP-VLK-MINI has 5 diff't keys so there's 11 options in my CDMenu, but 5 of them are all built from the XP-VLK-MINI.
Soooo------the catch is to follow directions correctly, and you don't have any issues.
Given:
c:\DVD
c:\DVD\SETUP\XP\XP-PRO-VLK
I create one DPACK .INI file for each folder underneath c:\dvd\setup\xp in DISC MODE
Then create one more more INI file in multiboot mode.
Make sure to select C:\DVD as the boot folder
Slipstream!
The results?
#1. C:\DVD\OEM created. This is the .7z'd DPacks......
#2. C:\DVD\SETUP\XP\XP-PRO-VLK\$OEM$ created if it's not there, and DPS ROE, etc, added.
NOW, run the create folders cmd.......
------------------------------------------
The only catch now, is I wish there was one place I could put my $OEM$ folder on the disk instead of one $OEM$ in every C:\DVD\Setup\XP\XP-PRO-VLK\$OEM$ and every os afterwards
However, I have an issue w/ DriverPacks currently.
First, my setup:
There's XP PRO VOL, XP PRO OEM, XP Home OEM, and XP Home RTL.
THere's different folders for the 5 different XP VOL Keys we have.
All of which have been integrated w/ RVM, and have some other packs applied, and are working swimmingly.
As you can tell from the screenshot, my current configuration includes and $OEM$ and OEM folder in each /Setup/XP/<folder>
These are the RVM packs everything was build from. Since the $OEM$ is exactly the same for all folders, CDImage is nice enough to save me a ton of space.
However, I don't know if that's the correct approach.....although I've verified it works.
More importantly, though, Driver Packs is NOT working, and I'm trying to figure out why.
Currently, the XP Source folders all have driver packs applied individually......and obviously work that way, as a single install CD.
However, when I put them in the multiboot, we're hosed
I don't know exactly how driver packs work yet, but I know there's a presetup.cmd, I just don't know how it's called.
From what I can tell currently, the only thing changed with the multiboot approach is that the TXTSETUP.SIF has one line changed
And although presetup.cmd is in the file, there is obviously something amuck w/ the current use of my OEM folder (automatically created by driver packs)
So, my questions are as follows:
#1. What is the most correct approach for the $OEM$ folder? One per setup source underneath the /Setup directory, or is there a better method
#2. Aside from trying driver packs w/ the multiboot approach, which is my next test, is there a way to make my current driver pack setup work properly?
And again, this thread kicks major butt. Thanks a ton.
My next step once I fix driver packs is to add on a slipstreamed 2K3 (Ent, Std, Web),and finally, a custom XPE (think Sherpya) buld I already have.
FYI, I did not have a need for using the install.cmd/<youros>.tag method because my apps are integrated already via SVCPack, regedts are imported via commands.txt and then I use WPI after installation.
Thanks for any reply.
Calpha.
PS. The create folders batch file blew my **** mind....looking at the source. And I'm a developer. I was totally impressed with the tricks applied in changing the file contents and never would have thought in a million years to do it........although admittedly, I don't understand the code exactly.......but am trying.
PSS. I will update when I try method 2 (multiboot apprach) with applying the driver packs.
Update: Driver Packs Working
I missed two things.
#1. Do Driver Packs Last. I was running the create_folders_.cmd on my Sources and then doing the driver packs. DOH!
#2. Bashrat's directions work perfectly for multiboot: I flummoxed the last try somehow, but they're working now.
Here's more clarification:
I have 6 Versions of XP currently.
These folders all exist at c:\dvd\setup\xp\
XP-VLK (RVM UpdatePack, 20+ Addons)
XP-VLK-MINI (RVM UpdatePack IE7, WMP11)
XP-OEM (RVM UpdatePack, 20+ Addons)
XP-OEM-MINI (RVM UpdatePack IE7, WMP11)
XPHomeOEM ( UpdatePack, 20+ Addons)
XPHomeRTL (UpdatePack, 20+ Addons)
From there, XP-VLK-MINI has 5 diff't keys so there's 11 options in my CDMenu, but 5 of them are all built from the XP-VLK-MINI.
Soooo------the catch is to follow directions correctly, and you don't have any issues.
Given:
c:\DVD
c:\DVD\SETUP\XP\XP-PRO-VLK
I create one DPACK .INI file for each folder underneath c:\dvd\setup\xp in DISC MODE
Then create one more more INI file in multiboot mode.
Make sure to select C:\DVD as the boot folder
Slipstream!
The results?
#1. C:\DVD\OEM created. This is the .7z'd DPacks......
#2. C:\DVD\SETUP\XP\XP-PRO-VLK\$OEM$ created if it's not there, and DPS ROE, etc, added.
NOW, run the create folders cmd.......
------------------------------------------
The only catch now, is I wish there was one place I could put my $OEM$ folder on the disk instead of one $OEM$ in every C:\DVD\Setup\XP\XP-PRO-VLK\$OEM$ and every os afterwards
This post has been edited by calpha: 07 June 2007 - 06:23 AM
#89
Posted 09 June 2007 - 06:55 PM
i just started making multiple boot cd's. i want to make bootable xp pro but i can't find "pro1.dat" file. cdshell does not find any file like name. how can i create this file. can you explane more how can i set cdshell... thank you...
This post has been edited by doktor001: 09 June 2007 - 07:09 PM
#90
Posted 10 June 2007 - 12:14 PM
doktor001, on Jun 9 2007, 06:55 PM, said:
i just started making multiple boot cd's. i want to make bootable xp pro but i can't find "pro1.dat" file. cdshell does not find any file like name. how can i create this file. can you explane more how can i set cdshell... thank you...
The files you're looking for are the .BIN files.
I just changed my cdshell entries to chain the .BIN and everything worked.
If you followed the example exactly, you would have a PRO1.BIN ----- and this file would be the loader that CDShell calls.
#91
- Amoguai
-
- Group: Members
- Posts: 196
- Joined: 25-November 05
- OS:Windows 7 x64
-
Country:
Posted 10 June 2007 - 06:15 PM
Hi calpha, thank you for the complements, really appreciated
So the major question is:
"What is the most correct approach for the $OEM$ folder? One per setup source underneath the /Setup directory, or is there a better method?".
Well, this guide was build with easy maintenance and performance in mind, avoiding the use of a $OEM$ folder, so we don't have to wait it's DVD-HD copy time, installing everything directly from DVD. Anyway, as far as i can remember, there is no way to access a $OEM$ folder outside the source itself, so we would have to stick with a $OEM$ folder for each source. However, if you really need a $OEM$ folder, you can simulate one, by just having a command to copy-paste a specified folder (what $OEM$ does) to the HD. But then again if you want to copy something from the DVD to the HD, just use the Install.cmd and you can use just one folder to keep your files in
See you soon
André Casal
So the major question is:
"What is the most correct approach for the $OEM$ folder? One per setup source underneath the /Setup directory, or is there a better method?".
Well, this guide was build with easy maintenance and performance in mind, avoiding the use of a $OEM$ folder, so we don't have to wait it's DVD-HD copy time, installing everything directly from DVD. Anyway, as far as i can remember, there is no way to access a $OEM$ folder outside the source itself, so we would have to stick with a $OEM$ folder for each source. However, if you really need a $OEM$ folder, you can simulate one, by just having a command to copy-paste a specified folder (what $OEM$ does) to the HD. But then again if you want to copy something from the DVD to the HD, just use the Install.cmd and you can use just one folder to keep your files in
See you soon
André Casal
This post has been edited by andregcasal: 16 August 2007 - 01:56 PM
#92
- Blah Face
-
- Group: Members
- Posts: 62
- Joined: 24-September 06
Posted 23 July 2007 - 03:13 AM
Hey!
Thanks for this! I can see alot of hard work has gone into it!
Right, im having problems tho.
Im trying to put on: XP Pro SP1 + SP2, XP Home SP1 + SP2, with them all tweaked in nLite v1.4b. (I only have Sp1, so I will have to use nLite to slipsttream SP2)
Ive tired this.
1.) Ripping Pro + Home to HDD, copying them, renaming them to SP2, ready to be updated.
2.) Applying "create_boot_folder.cmd". Which worked fine!
3.) Then on each of the OSs, did the nLite mods (all fine)
but when I came to be trying it out, in the XP setup on ALL the OSs, it was saying alot of files where missing! So then I deleted it all, and switch step 2 & 3 the other way around.
This also didn't work, this time on both SP1, it said that "ntkrnlmp.exe" with error code 14 (google didn't help out)
and with SP2, it said that please put in a floppy disk into A:, with XPSP2.
So when do I apply nLite then?
--some1
This is my Last Session.ini:
Thanks for this! I can see alot of hard work has gone into it!
Right, im having problems tho.
Im trying to put on: XP Pro SP1 + SP2, XP Home SP1 + SP2, with them all tweaked in nLite v1.4b. (I only have Sp1, so I will have to use nLite to slipsttream SP2)
Ive tired this.
1.) Ripping Pro + Home to HDD, copying them, renaming them to SP2, ready to be updated.
2.) Applying "create_boot_folder.cmd". Which worked fine!
3.) Then on each of the OSs, did the nLite mods (all fine)
but when I came to be trying it out, in the XP setup on ALL the OSs, it was saying alot of files where missing! So then I deleted it all, and switch step 2 & 3 the other way around.
This also didn't work, this time on both SP1, it said that "ntkrnlmp.exe" with error code 14 (google didn't help out)
and with SP2, it said that please put in a floppy disk into A:, with XPSP2.
So when do I apply nLite then?
--some1
This is my Last Session.ini:
[Main] Env = 1.4 beta - 2.0.50727.42.Microsoft Windows NT 5.1.2600 Service Pack 1 Target = Windows XP Home Edition SP:1 - 5.1.2600.1106 - English (United States) [Tasks] Remove Components Unattended Setup Hotfixes and Update Packs Tweaks Options [Components] ;# Keyboards # Albanian keyboard Arabic (101) keyboard Arabic (102) AZERTY keyboard Arabic (102) keyboard Armenian Eastern keyboard Armenian Western keyboard Azeri Cyrillic keyboard Azeri Latin keyboard Belarusian keyboard Belgian (Comma) keyboard Belgian (Period) keyboard Belgian French keyboard Bulgarian (Latin) keyboard Bulgarian keyboard Canadian French (Legacy) keyboard Canadian French keyboard Canadian Multilingual Standard keyboard Chinese (Simplified) - Microsoft Pinyin IME 3.0 keyboard Chinese (Simplified) - NeiMa keyboard Chinese (Simplified) - QuanPin keyboard Chinese (Simplified) - ShuangPin keyboard Chinese (Simplified) - US Keyboard keyboard Chinese (Simplified) - ZhengMa keyboard Chinese (Traditional) - Alphanumeric keyboard Chinese (Traditional) - Array keyboard Chinese (Traditional) - Big5 Code keyboard Chinese (Traditional) - ChangJie keyboard Chinese (Traditional) - DaYi keyboard Chinese (Traditional) - New ChangJie keyboard Chinese (Traditional) - New Phonetic keyboard Chinese (Traditional) - Phonetic keyboard Chinese (Traditional) - Quick keyboard Chinese (Traditional) - Unicode keyboard Chinese (Traditional) - US Keyboard keyboard Croatian keyboard Czech (QWERTY) keyboard Czech keyboard Czech Programmers keyboard Danish keyboard Devanagari - INSCRIPT keyboard Divehi Phonetic keyboard Divehi Typewriter keyboard Dutch keyboard Estonian keyboard Faeroese keyboard Farsi keyboard Finnish keyboard French keyboard FYRO Macedonian keyboard Gaelic keyboard Georgian keyboard German (IBM) keyboard German keyboard Greek (220) keyboard Greek (220) Latin keyboard Greek (319) keyboard Greek (319) Latin keyboard Greek keyboard Greek Latin keyboard Greek Polytonic keyboard Gujarati keyboard Hebrew keyboard Hindi Traditional keyboard Hungarian 101-key keyboard Hungarian keyboard Icelandic keyboard Irish keyboard Italian (142) keyboard Italian keyboard Japanese Input System (MS-IME2002) keyboard Japanese keyboard Kannada keyboard Kazakh keyboard Korean Input System (IME 2000) keyboard Korean keyboard Kyrgyz Cyrillic keyboard Latin American keyboard Latvian (QWERTY) keyboard Latvian keyboard Lithuanian IBM keyboard Lithuanian keyboard Marathi keyboard Mongolian Cyrillic keyboard Norwegian keyboard Polish (214) keyboard Polish (Programmers) keyboard Portuguese (Brazilian ABNT) keyboard Portuguese (Brazilian ABNT2) keyboard Portuguese keyboard Punjabi keyboard Romanian keyboard Russian (Typewriter) keyboard Russian keyboard Serbian (Cyrillic) keyboard Serbian (Latin) keyboard Slovak (QWERTY) keyboard Slovak keyboard Slovenian keyboard Spanish keyboard Spanish Variation keyboard Swedish keyboard Swiss French keyboard Swiss German keyboard Syriac keyboard Syriac Phonetic keyboard Tamil keyboard Tatar keyboard Telugu keyboard Thai Kedmanee (non-ShiftLock) keyboard Thai Kedmanee keyboard Thai Pattachote (non-ShiftLock) keyboard Thai Pattachote keyboard Turkish F keyboard Turkish Q keyboard Ukrainian keyboard United States-Dvorak for left hand keyboard United States-Dvorak for right hand keyboard United States-Dvorak keyboard United States-International keyboard Urdu keyboard US English Table for IBM Arabic 238_L keyboard Uzbek Cyrillic keyboard Vietnamese keyboard ;# Languages # ;Arabic Arabic (Algeria) Arabic (Bahrain) Arabic (Egypt) Arabic (Iraq) Arabic (Jordan) Arabic (Kuwait) Arabic (Lebanon) Arabic (Libya) Arabic (Morocco) Arabic (Oman) Arabic (Qatar) Arabic (Saudi Arabia) Arabic (Syria) Arabic (Tunisia) Arabic (U.A.E.) Arabic (Yemen) Divehi (Maldives) Syriac (Syria) Urdu ;Armenian Armenian ;Baltic Estonian Latvian Lithuanian ;Central Europe Albanian Croatian Czech Hungarian Polish Romanian Serbian (Latin) Slovak Slovenian ;Cyrillic Azeri (Cyrillic) Belarusian Bulgarian FYRO Macedonian Kazakh Kyrgyz (Kyrgyzstan) Mongolian (Mongolia) Russian Serbian (Cyrillic) Tatar Ukrainian Uzbek (Cyrillic) ;Georgian Georgian ;Greek Greek ;Hebrew Hebrew ;Indic Gujarati (India) Hindi Kannada (India) Konkani Marathi Punjabi (India) Sanskrit Tamil Telugu (India) ;Japanese Japanese ;Korean Korean ;Simplified Chinese Chinese (PRC) Chinese (Singapore) ;Thai Farsi Thai ;Traditional Chinese Chinese (Hong Kong S.A.R.) Chinese (Macau S.A.R.) Chinese (Taiwan) ;Turkic Azeri (Latin) Turkish Uzbek (Latin) ;Vietnamese Vietnamese ;Western Europe and United States Afrikaans Basque Catalan Danish Dutch (Belgium) Dutch (Netherlands) English (Australia) English (Belize) English (Canada) English (Caribbean) English (Ireland) English (Jamaica) English (New Zealand) English (Philippines) English (South Africa) English (Trinidad) English (Zimbabwe) Faeroese Finnish French (Belgium) French (Canada) French (France) French (Luxembourg) French (Monaco) French (Switzerland) Galician (Spain) German (Austria) German (Germany) German (Liechtenstein) German (Luxembourg) German (Switzerland) Icelandic Indonesian Italian (Italy) Italian (Switzerland) Malay (Brunei Darussalam) Malay (Malaysia) Norwegian (Bokmal) Norwegian (Nynorsk) Portuguese (Brazil) Portuguese (Portugal) Spanish (Argentina) Spanish (Bolivia) Spanish (Chile) Spanish (Colombia) Spanish (Costa Rica) Spanish (Dominican Republic) Spanish (Ecuador) Spanish (El Salvador) Spanish (Guatemala) Spanish (Honduras) Spanish (International Sort) Spanish (Mexico) Spanish (Nicaragua) Spanish (Panama) Spanish (Paraguay) Spanish (Peru) Spanish (Puerto Rico) Spanish (Traditional Sort) Spanish (Uruguay) Spanish (Venezuela) Swahili Swedish Swedish (Finland) ;# Multimedia # Music Samples Windows Media Player ;# Network # FrontPage Extensions MSN Explorer Windows Messenger ;# Operating System Options # Desktop Cleanup Wizard Search Assistant Tour Zip Folders ;# Services # Error Reporting ;# Compatibility # [KeepFiles] msconfig.exe [RemoveFiles] clock.avi yahoo.bmp swtchbrd.bmp [Options] CABMerge DisableMinMem DupeFiles ProfilesDir = "%SystemDrive%\Documents and Settings" TargetPath = "XP" temp_dir = %windir%\Temp NoWmpComp NoKeepCp AdvTweaks [Patches] TcpIp = 10 DoUxTheme DoSFC [Services2] Messenger,3 [Tweaks] Boot and Shutdown-Auto-End tasks immediately Boot and Shutdown-Auto-Kill hung applications immediately Boot and Shutdown-Auto-Kill hung services immediately Boot and Shutdown-Disable automatic restart on System Failure Boot and Shutdown-Disable logging on System Failure Boot and Shutdown-Do not Parse Autoexec.bat Boot and Shutdown-Numlock-On Boot and Shutdown-Status Messages-Extended Explorer-Add (un)register libraries in Context Menu Explorer-Advanced Search: preconfigure options Explorer-Associate additional file types with Notepad Explorer-Classic Control Panel Explorer-Disable Accessibility keyboard shortcuts Explorer-Disable Beep on errors Explorer-Disable Prefix: Shortcut to Explorer-Display the contents of system folders Explorer-Preset Places Bar to-Desktop, My Computer, Network Places, Documents and Pictures Explorer-Restore previous folder windows at logon Explorer-Show Drive Letters in front of Drive Names Explorer-Show extensions of known file-types Explorer-Show hidden files and folders Explorer-Show protected operating system files Explorer-Show the full path in the Address Bar Internet Explorer-Disable Download Complete notification Internet Explorer-Disable Internet Explorer link creation Internet Explorer-Disable Market Place bookmark Internet Explorer-Disable Media Player 6.4 created bookmarks Internet Explorer-Disable Outlook Express link creation Internet Explorer-Disable Password-Caching Internet Explorer-Enable Google URL-Search Internet Explorer-Set Homepage-www.google.com Internet Explorer-Set Internet Explorer to accept 10 connects at a time My Computer-Add Control Panel My Computer-Add Control Panel to Context Menu My Computer-Add Drive Cleanup to Context Menu My Computer-Add My Network Places My Computer-Add Network Connections My Computer-Add Printers and Faxes My Computer-Add Recycle Bin My Computer-Add Registry Editor to Context Menu My Computer-Add Scheduled Tasks My Computer-Add Software to Context Menu My Computer-Remove Search from Context Menu Network-Allow receiving Remote Assistance-Disable Network-Disable administrative shares Network-Remote Desktop-Disable Performance-Minimal Power Management Privacy-Remove Alexa Start Menu-Disable and remove Documents list from the Start Menu Start Menu-Disable popup on first boot Start Menu-My Network Places-Display as a link Start Menu-My Pictures-Don't display this item Start Menu-Network Connections-Display as Connect to menu Start Menu-Remove Search For People from Search Start Menu-Remove Search the Internet from Search Start Menu-Remove Set Program Access and Defaults Taskbar-Disable Language-Bar Taskbar-Hide Volume Control Icon in System Tray [Unattended] UnattendMode = 1 ComputerType = Default OOBEOff CustomLocales Resolution = 1024x768 BitsPerPel = 32 bit (True Color) DisableSRestore MaximumDataStorePercentOfDisk = 12 RestorePointLife = 30 DesktopTheme = Windows XP style|Silver|Normal size AutoUpdates = 4 AutoUDay = 5 AutoUHour = 15 ProgFilesPath = "\Program Files" CustomNetwork [NetAdapter1] connname = "" macaddress = "" ipaddress = "192.168.1.10" subnetmask = "255.255.255.0" defaultgateway = "192.168.1.1" dnsserver1 = "192.168.1.1" dnsserver2 = "" winsserver = "" netbiossetting = "0" ipxnetworknumber = "00000000" ipxnetworkframetype = "0xFF" [GuiRunOnce] [Drivers] [Hotfixes] F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\.NET Framework 1.1\NDP1.1sp1-KB867460-X86.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\.NET Framework 1.1\NDP1.1sp1-KB928366-X86.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Other\HMTCDWizard_enu.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Other\WindowsXP-KB896344-v2-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB923689-v2-x86-ENU.EXE F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Other\WindowsXP-KB914440-v12-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB912817-v2-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\msxml4-KB927978-enu.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Windows Media Player\WindowsMedia10-KB917734-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Windows Media Player\WindowsMedia-KB911564-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Windows Media Player\WindowsMedia6-KB925398-v2-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\msxml6-KB927977-enu-x86.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\.NET Framework 2.0\dotnetfx.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\.NET Framework 1.1\dotnetfx.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Other\gdidettool.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB914389-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB917537-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB918439-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB919007-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB917953-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB918118-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB914388-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB928255-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB911562-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB928843-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB929123-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB905749-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB913580-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB911927-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB908519-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB920213-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB924191-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB924270-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB926436-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB923980-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB926247-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB926255-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB924667-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB925902-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB920685-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB927802-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB920670-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB920683-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB923191-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB923414-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB927779-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB922819-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB886185-x86-enu.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB885836-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB931784-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB887472-x86-enu.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB891781-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB890859-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB888302-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB935839-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB935840-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB939373-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Internet Explorer 6.0\WindowsXP-KB929969-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\IE7-WindowsXP-KB933566-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB932168-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Internet Explorer 6.0\WindowsXP-KB933566-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB893756-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB901190-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB901017-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB900725-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB901214-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB905414-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB930178-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB904706-v2-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB899587-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB896428-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB896423-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB899591-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB931261-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB896358-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\.NET Framework 2.0\NDP20-KB917283-X86.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\.NET Framework 2.0\NDP20-KB928365-X86.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\.NET Framework 2.0\NDP20-KB922770-X86.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Other\Windows-KB909520-v1.000-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\IE7-WindowsXP-x86-enu.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\IE7-KB929969-WindowsXP-x86-enu.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB927891-v3-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Other\WindowsXP-KB936357-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Other\WindowsXP-KB931836-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB873339-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Other\WindowsXP-KB898461-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Other\WindowsXP-KB925876-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Other\WindowsXP-KB920342-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Other\WindowsXP-KB930916-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Other\WindowsXP-KB929338-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB900485-v2-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB920872-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB916595-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Other\WindowsInstaller-KB893803-v2-x86.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB922582-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB908531-v2-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB904942-v2-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB911280-v2-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB910437-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Critical Updates\WindowsXP-KB923789-x86-ENU.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Internet Explorer 6.0\WindowsXP-Windows2000-Script56-KB917344-x86-enu.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Windows Media Player\MP10Setup.exe F:\DVD\_Tools\Updates & Hotfixes\Windows XP x86 ENU\Windows Media Player\wmp11-windowsxp-x86-enu.exe
#93
- Advanced Member
-
- Group: Members
- Posts: 453
- Joined: 10-February 07
- OS:Windows 7 x64
-
Country:
Posted 10 August 2007 - 08:55 AM
can i use CDshell for a HDD? i am thinking of using a USB HDD to install XP from. a DVD might not be big enuf for programs to go into.
and also i seem to be missing winnt32.exe in i386 folder, isit bacause i removed "manual install & upgrage" in nLite? can i get it back? or must i redo the XP in nLite
Thanks
and also i seem to be missing winnt32.exe in i386 folder, isit bacause i removed "manual install & upgrage" in nLite? can i get it back? or must i redo the XP in nLite
Thanks
#94
- Amoguai
-
- Group: Members
- Posts: 196
- Joined: 25-November 05
- OS:Windows 7 x64
-
Country:
Posted 11 August 2007 - 08:05 AM
I believe you can use CDShell for bootup just about anything, just read the official site for more info. About winnt32.exe, yes, if you remove "manual install & upgrade" the file get's removed. You must redo your install.
Greetings,
André Casal
Greetings,
André Casal
#95
- Advanced Member
-
- Group: Members
- Posts: 453
- Joined: 10-February 07
- OS:Windows 7 x64
-
Country:
Posted 12 August 2007 - 01:00 AM
erm, how does
work?
folders are not created and there are no errors when running ...
my code
Quote
Automatically create multi-boot folders and files (thanks to geitonaki)
- Download geitonaki's SFX file
- Execute it and browse to your DVD folder. When finished it will open create_boot_folders.cmd, modify it to your needs.
- It will create the PRO1 boot folder, modify setupldr.bin, modify txtsetup.sif, create the PRO1.bin boot sector and copy the WIN51, WIN51IP and WIN51IP.SP1 (WIN51IP.SP2 if Service Pack 2) tag files.
- Download geitonaki's SFX file
- Execute it and browse to your DVD folder. When finished it will open create_boot_folders.cmd, modify it to your needs.
- It will create the PRO1 boot folder, modify setupldr.bin, modify txtsetup.sif, create the PRO1.bin boot sector and copy the WIN51, WIN51IP and WIN51IP.SP1 (WIN51IP.SP2 if Service Pack 2) tag files.
call create_boot_folder.cmd C:\DVD\SETUP\XP\Professional C:\DVD PRO1 FOO 0
work?
folders are not created and there are no errors when running ...
my code
call create_boot_folder.cmd C:\OS Deploy\DVD\SETUP\XPPROX2.1-DNP C:\OS Deploy\DVD PROX2.1DNP FOO 0
This post has been edited by iceangel89: 12 August 2007 - 01:01 AM
#96
Posted 16 August 2007 - 04:40 AM
Ohhh 
You are perfect. I really appricated.
Thank you soooo much.
You are perfect. I really appricated.Thank you soooo much.
#97
- Amoguai
-
- Group: Members
- Posts: 196
- Joined: 25-November 05
- OS:Windows 7 x64
-
Country:
Posted 16 August 2007 - 01:50 PM
Hi all,
iceangel89, you have all the info you need in geitonaki's post.
ysfozy, incentivation like yours keep me working harder, i'm glad to help
See you,
André Casal
iceangel89, you have all the info you need in geitonaki's post.
ysfozy, incentivation like yours keep me working harder, i'm glad to help
See you,
André Casal
This post has been edited by andregcasal: 16 August 2007 - 01:51 PM
#98
Posted 16 August 2007 - 04:29 PM
@andreqcasal
firstly thank you again I made almost 90% but there is a litte problem.
I just created XP, 2003 Standart and 2003 Enterprise. Regular setups are fine but when I press to "Unattended" nothing gonna happen Just like Regular setup, windows installation needs all informations.
Same here like Dunky12.
This is my Winnt.sif file:
i saved this sif file into PRO2. But nothing happening at the boot screen. It need time zone informations, formatting, bla, bla, bla
Thanks for your kindly help andreqcasal
firstly thank you again
I made almost 90% but there is a litte problem.I just created XP, 2003 Standart and 2003 Enterprise. Regular setups are fine but when I press to "Unattended" nothing gonna happen
Just like Regular setup, windows installation needs all informations.Same here like Dunky12.
This is my Winnt.sif file:
Quote
;SetupMgrTag
[Data]
AutoPartition=1
MsDosInitiated="0"
UnattendedInstall="Yes"
[Unattended]
UnattendMode=FullUnattended
OemSkipEula=Yes
OemPreinstall=No
TargetPath=\WINDOWS
Repartition=Yes
DetachedProgram="%SystemRoot%\System32\cmd.exe /c @ECHO something>%SystemDrive%\XPPRO.TAG"
[GuiUnattended]
AdminPassword=*
EncryptedAdminPassword=NO
OEMSkipRegional=1
TimeZone=130
OemSkipWelcome=1
[UserData]
ProductID=xxxxx-xxxxxxx-xxxxxxx-xxxxxxx-xxxxx
Fullname="adsdasasf"
Orgname="fafasafsfas"
ComputerName=*
[TapiLocation]
CountryCode=90
[RegionalSettings]
LanguageGroup=6
SystemLocale=0000041f
UserLocale=0000041f
InputLocale=041f:0000041f
[Identification]
JoinWorkgroup=WORKGROUP
[Networking]
InstallDefaultComponents=Yes
[Data]
AutoPartition=1
MsDosInitiated="0"
UnattendedInstall="Yes"
[Unattended]
UnattendMode=FullUnattended
OemSkipEula=Yes
OemPreinstall=No
TargetPath=\WINDOWS
Repartition=Yes
DetachedProgram="%SystemRoot%\System32\cmd.exe /c @ECHO something>%SystemDrive%\XPPRO.TAG"
[GuiUnattended]
AdminPassword=*
EncryptedAdminPassword=NO
OEMSkipRegional=1
TimeZone=130
OemSkipWelcome=1
[UserData]
ProductID=xxxxx-xxxxxxx-xxxxxxx-xxxxxxx-xxxxx
Fullname="adsdasasf"
Orgname="fafasafsfas"
ComputerName=*
[TapiLocation]
CountryCode=90
[RegionalSettings]
LanguageGroup=6
SystemLocale=0000041f
UserLocale=0000041f
InputLocale=041f:0000041f
[Identification]
JoinWorkgroup=WORKGROUP
[Networking]
InstallDefaultComponents=Yes
i saved this sif file into PRO2. But nothing happening at the boot screen. It need time zone informations, formatting, bla, bla, bla
Thanks for your kindly help andreqcasal
This post has been edited by ysfozy: 16 August 2007 - 04:30 PM
#99
Posted 17 August 2007 - 02:44 AM
Quote
if exist %SystemDrive%\XPPRO.TAG call :XPPRO
REM checks for the XPPRO2.tag and go to the corresponding section:
if exist %SystemDrive%\XPPRO2.TAG call :XPPRO2
REM checks for the SERVER2003.tag file and go to the corresponding section:
[if exist %SystemDrive%\SERVER2003.TAG call :SERVER2003
REM End
goto :end
REM checks for the XPPRO2.tag and go to the corresponding section:
if exist %SystemDrive%\XPPRO2.TAG call :XPPRO2
REM checks for the SERVER2003.tag file and go to the corresponding section:
[if exist %SystemDrive%\SERVER2003.TAG call :SERVER2003
REM End
goto :end
Why did we use "[if exist" there? Should it be "if exist"?
What is the difference between "if exist" and "[if exist"?
ALSO
I still couldn't do UNATTENDED 
This is my 14th hours. I did several ways, several modifies but nothing changed.Do you think why I couldn't it? Which file is calling "WINNT.SIF" file? Maybe that file is broken so WINNT.SIF couldn't calling from system.
EDIT:
I don't have:
Quote
%~dp0\Software\Program3.exe
%~dp0\Software\Program2.exe
%~dp0\Software\Program1.exe
%~dp0\Software\Program2.exe
%~dp0\Software\Program1.exe
and
Quote
%~dp0\Software\Tweak.reg
This can be problem?
FINALLY, I FOUND WHERE THE PROBLEM IS:
Quote
Add an Unattended option:
This section will teach you how to add an option which let's you install Windows unattendedly.
- Copy the PRO1 folder and PRO1.DAT file to "Copy of PRO1" and "Copy of PRO1.DAT"
- Rename it to PRO2 and PRO2.DAT
- Edit winnt.sif to include the unattended options.
This may be a good time to read the ref.chm file in Microsoft Deployment Too..
This section will teach you how to add an option which let's you install Windows unattendedly.
- Copy the PRO1 folder and PRO1.DAT file to "Copy of PRO1" and "Copy of PRO1.DAT"
- Rename it to PRO2 and PRO2.DAT
- Edit winnt.sif to include the unattended options.
This may be a good time to read the ref.chm file in Microsoft Deployment Too..
This way is completely useless for my bootdisk:
Quote
- Copy the PRO1 folder and PRO1.DAT file to "Copy of PRO1" and "Copy of PRO1.DAT"
- Rename it to PRO2 and PRO2.DAT
- Rename it to PRO2 and PRO2.DAT
Main idea is this: When you copy and renamed like PRO2 and PRO2.DAT, PRO2.DAT don't see "PRO2", it still see "PRO1". So that, if you want to create a UNATTENDED version, you have to do same things like doing in PRO1. I mean you have to use Create_boot_folders.cmd for PRO2 too.
Thanks to andreqcasal again for this greate guide.
This post has been edited by ysfozy: 17 August 2007 - 03:05 AM
#100
- Amoguai
-
- Group: Members
- Posts: 196
- Joined: 25-November 05
- OS:Windows 7 x64
-
Country:
Posted 20 August 2007 - 09:22 AM
ysfozy, on Aug 17 2007, 09:44 AM, said:
This way is completely useless for my bootdisk:
Main idea is this: When you copy and renamed like PRO2 and PRO2.DAT, PRO2.DAT don't see "PRO2", it still see "PRO1". So that, if you want to create a UNATTENDED version, you have to do same things like doing in PRO1. I mean you have to use Create_boot_folders.cmd for PRO2 too.
Quote
- Copy the PRO1 folder and PRO1.DAT file to "Copy of PRO1" and "Copy of PRO1.DAT"
- Rename it to PRO2 and PRO2.DAT
- Rename it to PRO2 and PRO2.DAT
Main idea is this: When you copy and renamed like PRO2 and PRO2.DAT, PRO2.DAT don't see "PRO2", it still see "PRO1". So that, if you want to create a UNATTENDED version, you have to do same things like doing in PRO1. I mean you have to use Create_boot_folders.cmd for PRO2 too.
Sorry for the late reply, i am on vacations and i am using someone's wireless network with my laptop (ssshhh)
Major mistake by me, forgot to update that section of the guide when i implemented the Create_boot_folders.cmd, many thanks for your input ysfozy! There are two ways to go around that problem, reusing the Create_boot_folders.cmd or by manually editing setupldr.bin in the PRO2 folder so that all references to PRO1 now point to PRO2, and hex-edit PRO2.DAT so that it points to PRO2 as well (wich is kinda easy). I will update the guide as soon as i can, thanks again ysfozy
This post has been edited by andregcasal: 20 August 2007 - 09:23 AM
#101
Posted 01 September 2007 - 11:40 PM
Hello those days I'm trying to make a multi-boot dvd with this content:
- XP Pro (Normal) - spanish
- XP Pro Service Pack 2 - spanish
- XP Pro Service Pack 2 + Updates + WPI - spanish
- Ultimate Boot CD (latest version)
- Norton Ghost 12 (with the ability to boot the recovery system)
I've readed your guides and I've get the first 3 to work (3 XP + WPI + CDShell), but the problem is that I don't know how to integrate the other two. I want to be able to boot from UBCD folder and the GHOST folder too, from the CDSHELL menu. When I did the Isobuster step (for extracting the boot image) for these two boot images and then tried to open them in hexworkshop, the application showed me an error ' The parameter is not correct'. The same occurs in other hex editors.
Also, I dont know what to do with these two boot images...
I have this folder structure:
______________________________
BOOT
|
SYSTEMS
|
----------XP
----------XPSP2
----------XPSP2WPI
|
SYSTOOLS
----------UBOOTCD
----------NGHOST12
|
SOFTWARE
----------*software folders*
|
*wpi folders*
______________________________
Could you help me please? Thank you very much.
- XP Pro (Normal) - spanish
- XP Pro Service Pack 2 - spanish
- XP Pro Service Pack 2 + Updates + WPI - spanish
- Ultimate Boot CD (latest version)
- Norton Ghost 12 (with the ability to boot the recovery system)
I've readed your guides and I've get the first 3 to work (3 XP + WPI + CDShell), but the problem is that I don't know how to integrate the other two. I want to be able to boot from UBCD folder and the GHOST folder too, from the CDSHELL menu. When I did the Isobuster step (for extracting the boot image) for these two boot images and then tried to open them in hexworkshop, the application showed me an error ' The parameter is not correct'. The same occurs in other hex editors.
Also, I dont know what to do with these two boot images...
I have this folder structure:
______________________________
BOOT
|
SYSTEMS
|
----------XP
----------XPSP2
----------XPSP2WPI
|
SYSTOOLS
----------UBOOTCD
----------NGHOST12
|
SOFTWARE
----------*software folders*
|
*wpi folders*
______________________________
Could you help me please? Thank you very much.
#102
- Amoguai
-
- Group: Members
- Posts: 196
- Joined: 25-November 05
- OS:Windows 7 x64
-
Country:
Posted 02 September 2007 - 02:41 AM
Hi eevox!
Well, in lack of better option, you can try to download the *.IMA file from those 2 programs. The integration with CDShell is pretty easy. Windows 98 also boots from a *.IMA file, so if you go to the guide made by chon_ you would find this as the code to boot the *.IMA:
print "2) Windows 98 \n"
...
if $lastKey == key[2]; THEN DISKEMU /Setup/BootSect/Win98.IMA
Good Luck,
André Casal
Well, in lack of better option, you can try to download the *.IMA file from those 2 programs. The integration with CDShell is pretty easy. Windows 98 also boots from a *.IMA file, so if you go to the guide made by chon_ you would find this as the code to boot the *.IMA:
print "2) Windows 98 \n"
...
if $lastKey == key[2]; THEN DISKEMU /Setup/BootSect/Win98.IMA
Good Luck,
André Casal
This post has been edited by andregcasal: 02 September 2007 - 02:41 AM
#103
- Blah Face
-
- Group: Members
- Posts: 62
- Joined: 24-September 06
Posted 05 January 2008 - 06:04 AM
How can I add a bootscreen to this!?
not using the boot.ini trick!?
not using the boot.ini trick!?
This post has been edited by some1: 05 January 2008 - 06:09 AM
#104
Posted 08 January 2008 - 04:09 PM
I've got problem with asms errors. I was looking for and I discovered that the problem is caused by cdimage and I tested it and it was true.
Does someone know how to create the image with mkisofs? I tried
Thanks
Does someone know how to create the image with mkisofs? I tried
mkisofs.exe -J -l -r -boot-load-size 4 -o "D:/AIODVD.iso" -b "BOOT/loader.bin" -no-emul-boot -volid "XPSP2" "D:/DVD/"and works but when I select pro1.bin or pro2.bin It doesnt work.
Thanks
#105
- Amoguai
-
- Group: Members
- Posts: 196
- Joined: 25-November 05
- OS:Windows 7 x64
-
Country:
Posted 08 January 2008 - 08:23 PM
some1, on Jan 5 2008, 01:04 PM, said:
How can I add a bootscreen to this!?
not using the boot.ini trick!?
not using the boot.ini trick!?
DryKillLogic, on Jan 8 2008, 11:09 PM, said:
I've got problem with asms errors. I was looking for and I discovered that the problem is caused by cdimage and I tested it and it was true.
Does someone know how to create the image with mkisofs? I tried
Thanks
Does someone know how to create the image with mkisofs? I tried
mkisofs.exe -J -l -r -boot-load-size 4 -o "D:/AIODVD.iso" -b "BOOT/loader.bin" -no-emul-boot -volid "XPSP2" "D:/DVD/"and works but when I select pro1.bin or pro2.bin It doesnt work.
Thanks
Good luck,
André Casal
