|
Post Number: 1
|
apsolus 

Group: Members
Posts: 16
Joined: Aug. 2009
|
 |
Posted on: Aug. 13 2009,07:28 |
|
 |
QUOTE 6) Start EasyBoot, click 'Tools'->'Replace Text', browse file 'c:\easyboot\disk1\ezboot\xpen.bin', and specify 'I386' as "Text to Replace", 'XPEN' as "Replace to", then click 'Replace', 1 occurence should be replaced 7) Do step 6 to 'c:\easyboot\disk1\xpen\setupldr.bin', and replace 'i386' to 'xpen', 4 occurences should be replaced
Hi guys, ive been trying this awhile now but havent been able to figure out what to do. Step 6 works fine, 1 thing is changed, but when I try step 7, nothing gets changed, says 0 strings replaced.
I've been trying to make a multi-boot XP CD, and a XP/Win2k CD, and all the data is clean and hasnt been altered by any program when I start the process. I can burn the CD there after, and once I chose an option is goes to "press any Key to boot from CD" then screen flashes 2x and computer restarts.
Any ideas? any and all help would be appreciated, thanks.
|
 |
|
|
Post Number: 2
|
madar 

Group: Members
Posts: 153
Joined: Apr. 2009
|
 |
Posted on: Aug. 13 2009,08:33 |
|
 |
apsolus
This is an error in EasyBoot that i have been encontered several times.
I think it is better to use other hex editor to change strings like i do.
-------------- Shirin Zaban
|
 |
|
|
Post Number: 3
|
apsolus 

Group: Members
Posts: 16
Joined: Aug. 2009
|
 |
Posted on: Aug. 13 2009,09:13 |
|
 |
How do I got about that? Last time i used one things didnt go to well lol, could you be more specific?
|
 |
|
|
Post Number: 4
|
madar 

Group: Members
Posts: 153
Joined: Apr. 2009
|
 |
Posted on: Aug. 13 2009,10:58 |
|
 |
For example you need to change some strings in xpen.bin 1st you should have an hex editor,i use small and free "Hex Edit" open xpen.bin (in your example) by for example "Hex Edit" search for "i386" and changes that by xpen you will have normally more than one i386 ,change all of them,then save it
that's all you need to do
If you need more help and if i could not understand your question very well inform me please
Edited by madar on Aug. 13 2009,10:59
-------------- Shirin Zaban
|
 |
|
|
Post Number: 5
|
apsolus 

Group: Members
Posts: 16
Joined: Aug. 2009
|
 |
Posted on: Aug. 13 2009,17:04 |
|
 |
I followed your advice and gave it a shot, and the same thing as before happens the last time I tried a hex editor, it says it cannot find any strings for I386.
Any ideas? this isnt with just one windows install either, and each time I try and make a disc, i start off with unmodified files.
|
 |
|
|
Post Number: 6
|
madar 

Group: Members
Posts: 153
Joined: Apr. 2009
|
 |
Posted on: Aug. 13 2009,17:58 |
|
 |
apsolus
1.Some hex editors are sensetive for uppercase and lowercase characters. do not use this kind of hex editors or at least search for "i386" and also "I386" by this kind of hex editors.
2.hex edit that i said is not sensetive for upper and lowercase
3.may be xpe.bin that you use is currupted so use other one
-------------- Shirin Zaban
|
 |
|
|
Post Number: 7
|
apsolus 

Group: Members
Posts: 16
Joined: Aug. 2009
|
 |
Posted on: Aug. 13 2009,18:08 |
|
 |
As ashamed I am to admit it, you were correct, I was not using the proper case it seems, and for odd reason, I did not think about that. Thank you very much for all your help Madar, I have read a few of your other posts as well, since I also intend on making a multi boot diagnostic CD w/ Acronis, UBCD etc on it. Going to compile this multi xp cd now and see if it works, I'll let you know how it goes.
Again, thank you very much ^^
|
 |
|
|
Post Number: 8
|
apsolus 

Group: Members
Posts: 16
Joined: Aug. 2009
|
 |
Posted on: Aug. 13 2009,19:33 |
|
 |
Well I was able to assemble the DVD without much trouble, the w2ksect.bin oddly no longer listed any i386 entries regardless of me not altering that file, but I just made dups of the XPEN.bin and renamed it and altered it to my needs. I burned the image, the menu's and everything works fine, however, during the driver loading process, on 2 of the 4 CDs (HP and Dell) I get iaStor.sys could not be found and am forced to restart. On the Gateway one, I received the same message, however the first attempt it was a different file missing. And for the standard XP SP3 CD I just get a blue screen 0x0000007B after it finishes loading the drivers.
I've read for a BartsPE CD using OEM CDs such as ones from Dell, Compaq etc, people have had similar issues, however I cannot find a solution in the postings.
I was thinking of copying the files into each directory but am unsure if that would fix the problem, or if more would arise. Any ideas? thanks
|
 |
|
|
Post Number: 9
|
madar 

Group: Members
Posts: 153
Joined: Apr. 2009
|
 |
Posted on: Aug. 13 2009,20:12 |
|
 |
apsolus
1_ for xp sp3 version you should have files below in root of your CD / DVD and also inside your xp folders (for example xpen) if you do not,you will get blue page error: WIN51 WIN51IP WIN51IP.SP1 WIN51IP.SP2 WIN51IP.SP3
2.It is good to take a look at link below too
http://www.ezbsystems.com/cgi-bin/ikonboard.cgi?act=ST;f=1;t=2774;st=0
-------------- Shirin Zaban
|
 |
|
|
Post Number: 10
|
apsolus 

Group: Members
Posts: 16
Joined: Aug. 2009
|
 |
Posted on: Aug. 13 2009,21:27 |
|
 |
QUOTE WIN51 WIN51IP WIN51IP.SP1 WIN51IP.SP2 WIN51IP.SP3
I have all of those files, except the .SP1 one, which is not located even on my original source CDs.
I was able to figure out my missing file problem, I copied all the sys files from i386 and pasted them into each XP root folder and that fixed that problem.
The only problem that remains is that blue screen. It does not appear on older machines, such as a Dell C640 laptop, but if I put the CD into a newer machine such as my laptop, Asus G50v, I'll get the blue screen. It has an Intel based Chipsets and SATA controller, ICH10, I never install the iastor.sys files onto the CDs myself (originally) so I am wondering if they need to be updated and is causing the error since they may be to old to be used as the controller regardless of loading anyhow?
I do thank you for the link Madar, that is exactly the first guide I used as well when I first started making multi-boot CDs
|
 |
|
|
|
|