Jump to content

amd64lover

Member
  • Posts

    153
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by amd64lover

  1. lol... if you dont want to boot from the CD, then take it out...
  2. if you wait like 20 seconds or so, itll boot from the hard drive. or if you wanted, you could add an option to the boot menu to go boot from the hdd.
  3. make sure the CDROM_IP files are in there....
  4. it should say if $lastKey == key[9]; then memdisk /4230.IMG ... (and no need to double post)
  5. was it a 24-bit 640 x 480 BMP file you tried to convert? please explain more on what went wrong...
  6. quote from Flyakite's guide... Multiple OS Boot Options But wait, there is more! Most of us who are taking on a project such as this will probably be using our DVD to help our friends/family/co-workers. So if we are re-installing XP on someone else's computer, we don't want all of our unattended information and programs being installed as well. Luckily, there is a simple fix to this. To allow ourselves to be able to install a regular OS installation or an unattended installation, we will need multiple boot options for that OS. To do this, we must create multiple boot folders and boot sectors. Taking XP as the example, copy the PRO1 folder, paste it back into the AIO-DVD folder and rename it from Copy of PRO1 to PRO2. Do the same thing with PRO1.DAT and rename it to PRO2.DAT. So now we should have two folders and two DAT files with the same contents: D:\AIO-DVD\PRO1\ D:\AIO-DVD\PRO2\ D:\AIO-DVD\PRO1.DAT D:\AIO-DVD\PRO2.DAT Now we need to edit 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. If you want the first boot option to be a regular installation and the second option to be an unattended installation, add your winnt.sif file to the PRO2 folder. All that's left is to add the correct entries to our boot menu so we can select different installation options. The following is an example of what I mean: XP_Pro: print c "\n\cXXMicrosoft Windows XP Professional SP1 Corporate \n" print "1) Regular \n" print "2) Unattended \n" XP_Pro_Key: if $lastKey == key[1]; then chain /PRO1.DAT if $lastKey == key[2]; then chain /PRO2.DAT
  7. quote from Flyakite's guide... Multiple OS Boot Options But wait, there is more! Most of us who are taking on a project such as this will probably be using our DVD to help our friends/family/co-workers. So if we are re-installing XP on someone else's computer, we don't want all of our unattended information and programs being installed as well. Luckily, there is a simple fix to this. To allow ourselves to be able to install a regular OS installation or an unattended installation, we will need multiple boot options for that OS. To do this, we must create multiple boot folders and boot sectors. Taking XP as the example, copy the PRO1 folder, paste it back into the AIO-DVD folder and rename it from Copy of PRO1 to PRO2. Do the same thing with PRO1.DAT and rename it to PRO2.DAT. So now we should have two folders and two DAT files with the same contents: D:\AIO-DVD\PRO1\ D:\AIO-DVD\PRO2\ D:\AIO-DVD\PRO1.DAT D:\AIO-DVD\PRO2.DAT Now we need to edit 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. If you want the first boot option to be a regular installation and the second option to be an unattended installation, add your winnt.sif file to the PRO2 folder. All that's left is to add the correct entries to our boot menu so we can select different installation options. The following is an example of what I mean: XP_Pro: print c "\n\cXXMicrosoft Windows XP Professional SP1 Corporate \n" print "1) Regular \n" print "2) Unattended \n" XP_Pro_Key: if $lastKey == key[1]; then chain /PRO1.DAT if $lastKey == key[2]; then chain /PRO2.DAT
  8. it should tell you what line the error is on....
  9. did you edit the XP64.DAT file to point to the XP64 folder?
  10. hmmmm.... is the boot folder in the root named 'XP64'? did you copy the entire cd to the \SETUP\XP64\ directory?
  11. it happens... glad to see its working.
  12. i forgot to delete it... unless we are running the exact same version of XP64, the winnt.sif file wont work (or at least the cdkey in there wont work). correct, if you use this boot folder, then copy the entire installation cd to the \SETUP\XP64 directory. be sure to edit the XP64.DAT file as well.
  13. i am not sure what you are asking... the loader.BIN file should be in the Boot folder and is used to make the dvd bootable. as far as the firewall, you may have selected the option to turn it off in the Nlite options.
  14. that is probably what it is since that command is looking for the loader.bin file in the BOOT folder. if all other things are equal, it should look like this... start cdimage.exe -lAIODVD -t08/23/2001,09:00:00 -b\AIO-DVD\CDSH\loader.bin -h -n -o -m \AIO-DVD C:\AIODVD.iso
  15. ok, if it flashes up a screen then does nothing, it means a parameter is incorrect. double check your folder names/spellings and locations of files, then try it again.
  16. what do you mean stopped working? please be more specific about exactly what happens...
  17. i would say go back and double check and re-read carefully to make sure you didnt overlook anything...
  18. ok, i think i got it figured it out... i tried this in a virtual drive and loaded the ISO into VMware and it worked fine...the problem was that the locations of the files being called were different when on CD than when run from the hard drive...i put all the .BAT files i created in the BOOT directory (same directory as the cdimage.exe). here is the code i used to create the XP standalone ISO... start BOOT\CDIMAGE.EXE -lVRMPVOL_EN -t08/23/2001,09:00:00 -b..\SETUP\XP\BOOT.BIN -h -n -o -m ..\SETUP\XP "C:\Documents and Settings\All Users\Desktop\Windows XP Pro.iso" note that even though the .BAT file is in the same directory as the cdimage, i still had to specify the location as BOOT/CDIMAGE.EXE instead of just specifying the file name. i believe this is because the command prompt is being run from the 'F:' drive (my cdrom drive) and not the exact folder the file is in. keeping that in mind, i just used the '..\' to make it go back to the root of the disc, and then gave the location of the necessary files from there. i tried it out and it works great (although it doesnt work when run directly from the hard drive, but then again, it doesnt need to). let me know if this works for anyone else.
  19. well i am not sure if adding both the i386 and amd64 folders in the XPX64EN folder is problematic. try creating an "XP64" folder in your setup folder (or whatever folder contains the installation files for the other OSes) and copying the entire xp64 installation cd to that folder. in addition to the edits you have made above, be sure to edit the boot image. i have uploaded my boot folder (you may want to delete the winnt.sif thats in there). it can be downloaded at http://rapidshare.de/files/6724995/XP64.zip.html
  20. you do not need an I386 and AMD64 at the root of your DVD... obtain the boot folder, $WIN_NT$.~BT, rename it, then edit the setupldr.bin/txtsetup.sif files...
  21. that sounds like you forgot to copy the WIN51IA to the root of the DVD... yes, there are 7 instances of 'i386' (case insensitive) being matched. as for unattended, be sure to include the winnt.sif file in both the boot folder and the amd64 folder (in the setup directory).
  22. try obtaining the boot files the regular way. also, the $OEM$ folder isnt needed for an unattended setup. just make sure the winnt.sif file you created is in both the boot folder and actual i386 folder.
  23. De cual parte de espana eres? he ido a espana dos veces y me encanta mucho... just to double check, did you correctly edit the txtsetup.sif file, delete the correct files in the boot folder, and edit the setupldr.bin file?
  24. well, follow flyakites guide (http://flyakite.msfnhosting.com/) and then edit the files as necessary. the steps are about the same for both the 32 and 64bit versions of windows. be sure to use VMware or something similar to obtain the boot files for xp64. then read this.... "i also found that the 'XP64' and 'PRO64' are not necessary. Just take the boot folder ($WIN_NT$.~BT) and rename it to something else (i did mine to XP64) and then edit the setupldr.bin file & replace all instances of "I386" with "XP64", then edit the boot image to show XP64 instead of i386. this is a way to have 1 less folder in your root. i have the x64 boot folder if anyone needs it." read through the forums and youll have a lot of questions answered. let me know how it works.
×
×
  • Create New...