|
|
| Post Number: 1
|
Zardoz2293 
Group: Members
Posts: 6
Joined: Sep. 2004
|
 |
Posted on: Sep. 05 2004,21:42 |
|
   |
Gentlemen, I have read the posts for EasyBoot and UltraISO many, many times in the past week (including the winhelp for each product) and consider myself an expert in that regard. Â However, I am completely unable to create a bootable WinXP Setup [note: using ISO from MSDN {origin is a dual setup boot xp home/xp professional ISO; disc #2429.1 Nov-2003} (including Acronis True Image 8/DriveCleanser 6) using EasyBoot. Â I have had various successes but always one error or another. Â The best solution to date was a posting from eureka which works for FAT but I use NTFS on all my systems -- so not a solution for me (I would expect that there are many others with the same conditions). Â I have extensive systems background knowledge but I haven't worked with ISO images to create bootable discs with multiple products on one physical media. Â Having the ability to create an IMA image and boot it allows for significant control with minimal effort and with excellent results (so far 100% success). Â However, using the BIN is where I am completely mystified. Â I have searched and cannot find any product available that will read and extract and/or inject files using a BIN (I have checked over two dozen products in the past week with negative results).
I read about copy the XYZ.BIN into the "\EasyBoot\disk1\ezboot" folder and in EasyBoot execute it via the menu command of "run XYZ.BIN". Â I also read '...copy the contents into the "\disk1" folder.' Â I find this completely confusing as if I have many products on one physical disc then it will be total confusion at the "\disk1" folder location with future maintenance impossible as well as potential and expected conflicts with other products (older and different versions of extracted ISO files). Â I also read '...you can create "\disk1" and "\disk2", etc. for each product you have.' Â Which is even further confusing as to how does EasyBoot access these folders? Â After XYZ.BIN is executed exactly what occurs NEXT? Â Does EasyBoot change to the folder at "\disk1\XYZ" and would it execute config.sys and autoexec.bat?
Further, I have a lot of files in my "ezboot" folder and with the 8.3 filename limitation it is hard to read even with naming system. Â Attempted to create folders for each class of IMA/BIN and add the folder to the EasyBoot menu run command but failed in the results. Â Is there a way to do this? Â I know about the ";" syntax for in the "run" command -- would this achieve any of the above issues?
Thanks!
|
 |
|
|
| Post Number: 2
|
xoben
Group: Super Administrators
Posts: 849
Joined: Nov. 2003
|
 |
Posted on: Sep. 06 2004,03:12 |
|
 |
| Quote | | Further, I have a lot of files in my "ezboot" folder and with the 8.3 filename limitation it is hard to read even with naming system. Attempted to create folders for each class of IMA/BIN and add the folder to the EasyBoot menu run command but failed in the results. Is there a way to do this? I know about the ";" syntax for in the "run" command -- would this achieve any of the above issues? |
Please do it this way:
1) making a folder c:\easyboot\disk1\myboot (or other name as you like)
2) coping your xxx.img/bin there, for example 123.img
3) Using "cd /;cd myboot;run 123.img" as menu command
Note: You should change the working directory for EB before using a boot file located at another place than default (/ezboot).
| Quote | | I read about copy the XYZ.BIN into the "\EasyBoot\disk1\ezboot" folder and in EasyBoot execute it via the menu command of "run XYZ.BIN". I also read '...copy the contents into the "\disk1" folder.' I find this completely confusing as if I have many products on one physical disc then it will be total confusion at the "\disk1" folder location with future maintenance impossible as well as potential and expected conflicts with other products (older and different versions of extracted ISO files). I also read '...you can create "\disk1" and "\disk2", etc. for each product you have.' Which is even further confusing as to how does EasyBoot access these folders? After XYZ.BIN is executed exactly what occurs NEXT? Does EasyBoot change to the folder at "\disk1\XYZ" and would it execute config.sys and autoexec.bat? |
1) "\disk1" is the root directory of your bootable CD/DVD, you should put all your files and folders there
"\disk1\ezboot" is the defualt folder for holding boot files
you can make as many folders as needed under "\disk1". EB does not care contents under these folders, but put all of them into your bootable ISO
2) Sometimes, .BIN extension is also used for CD image files, but EB supports only floppy image and binary files such as w2ksect.bin. .EXE/.BAT files do not work as well.
|
|
|
|
| Post Number: 3
|
eureka
Unregistered
|
 |
Posted on: Sep. 06 2004,08:07 |
|
|
Quote Zardoz2293: “Further, I have a lot of files in my "ezboot" folder and with the 8.3 filename limitation it is hard to read even with naming system…”
Good point.
Zardoz2293 Please read my last response on your request concerning “Make a Windows Win98/2000/XP 3-1-1 bootable CD”. Please Test it, because I only owns 2000server, not 2003server as an example.
Final note: I want to say thanks to xoben for some god advices. It’s getting better and better…
|
|
|
|
| Post Number: 4
|
Zardoz2293
Group: Members
Posts: 6
Joined: Sep. 2004
|
 |
Posted on: Sep. 17 2004,15:32 |
|
|
Gentlemen,
I have been pulling out my hair for the past three weeks now and I still can't get a Windows XP 2002 Professional [Retail] Slipstreamed with SP-2 to work. Â I have started from ground zero to make sure something wasn't corrupt. Â Currently I either get "NTLDR" error (fixed, using all upper case replacement of 4 char "I386" in references) and now the new "ozone" where it goes blank screen for a while then reboot.)
Question: Has anyone successfully Slipstreamed SP-2 on XP Professional Retail (OR MSDN ISO version, I can live with either).
I have extensive systems background and I feel like a neophyte with this one. Â
NOTE: At one point I was using the MSDN ISO version and had everything working until it asked for the Full Retail Installed Version Verification. Â Which defeats why I need this boot kit. Â (Yes, I have all legal / licensed products.) Â Further reading about MSDN ISO w/ or w/o SP2 slipstreamed said that the verification could not be avoided or removed. Â [Now this may be true or not currently I am assuming it is true] Â I just want to get a SINGLE XP-SP2 PRO [RETAIL] EasyBoot w/ NTFS formatted HD access to work (I know this last part will as I have gotten it to work before].
I just can't seem to find what I would call a "scientific" method to reproduce the procedure that results in 100% success each time.
Further I have this one comment to say about an Enhancement to EasyBoot. Â Is there some technical reason why EasyBoot can't have a command that allow you to change or select what folder is the "\disk1" ? Â Why? Â Well if you could say create "\WXPP" at the same level of "\disk1" and you could tell EasyBoot to use that as the "root" then everyone wouldn't have to make any changes to various files to get complex ISO images to work. Â Command like: "cdfix \WXPP;run w2kboot.bin" Â Under the folder "\WXPP" you would have an exact copy of the source, so "I386" would be there and all the unmodified files. Â This would also allow for having many, many complex boot configurations ("\WXPP" (xp pro); "\WXPH" (xp home); "\WXPS" (xp 2003 server); etc.) Just food for thought.
Edited by Zardoz2293 on Sep. 17 2004,15:40
|
|
|
|
| Post Number: 5
|
Eureka
Unregistered
|
|
Posted on: Sep. 17 2004,17:38 |
|
|
Well, Zardoz2293.
Sorry to say that you seems to have right. I do agree with you Zardoz2293 (in most part of your arguments). And, yes I also have the same troubles with Xp_servicepack-2 in combination with NTFS (servicepack-1a works perfect with NTFS and EasyBoot).
However as I earlier have proved; everything can still be installed thru FAT32. I now that’s not a solution for you – only want to pointing on a “target way” to get around the problems.
What a perfect tool wouldn’t EasyBoot be, if it were possible to use the ISO-file itself (boot from it as ISO-file)? But this is reality. And please… do not, he, he pull out your hair – there is still hope….
Maybe Xoben can “pull out his hair” and guide as all to a - if not perfect - so at least a reasonable solution?
|
|
|
|
|
|
|
© 2002-2024 EZB Systems, Inc.
|
|
|
