|
|
| Post Number: 1
|
bodycode 
Group: Members
Posts: 3
Joined: Oct. 2004
|
 |
Posted on: Oct. 14 2004,15:46 |
|
   |
These 2 errors were encountered Using version 5.0.3.426.
The following errors were found after burning to a DVD+RW
1) File not found when booting from burned DVD+RW for BOTH operating systems.
2) While doing search n' replace for "adding windows 2000", search and replace only found 3 occurances of i386, not 4, as mentioned in the "practical guide". for making an Nin1 DVD.
Everything else went perfectly accourding to the instructions. My source OS's were XP Pro and Win2k. When booting the DVD+RW I get "file not found" after OS install selection for BOTH win2k and XP! Why is this? Thanks in advance.
|
 |
|
|
| Post Number: 2
|
The Hitchhiker
Unregistered
|
|
Posted on: Oct. 15 2004,11:20 |
|
 |
!BodyCode
"File not found" error is displayed by easyboot, when the file you use with the "run xxx" command in menu isn't a existing filename in the disk1\ezboot subfolder.
This should be for example a w2k.bif (modified bootsector of a w2k cd) and the wxp.bif.
|
|
|
|
| Post Number: 3
|
bodycode
Group: Members
Posts: 3
Joined: Oct. 2004
|
|
Posted on: Oct. 16 2004,00:13 |
|
|
Ah! Thanks I'm going to thorougly check the naming conventions. Not only that but I think I had "show file extensions" set to off, which would give me bin.bin files. tHat's a no no 
I see what you mean. I'm going to look into this throughly.
Thanks for nice hint.
Regards,
Marshall
|
|
|
|
| Post Number: 4
|
bodycode
Group: Members
Posts: 3
Joined: Oct. 2004
|
|
Posted on: Oct. 16 2004,00:47 |
|
|
| Quote (Guest @ Oct. 15 2004,16:20) | !BodyCode
"File not found" error is displayed by easyboot, when the file you use with the "run xxx" command in menu isn't a existing filename in the disk1\ezboot subfolder.
This should be for example a w2k.bif (modified bootsector of a w2k cd) and the wxp.bif. |
Ok. I fixed that. The problem is with the original instructions found in the "practical manual". Actually, a person must "show file extensions" in all versions of Windows, or else, you'll get stuff like *.bin.bin which is not good and will certainly lead to the problem I've been having! I can't believe that every person who uses the software doesn't get that.
Now, all I get when I select iinstall windows 2000 is "CDBOOT: couldn't find NTDLR". Any ideas on that? The XP install selection works like a charm. Thanks
|
|
|
|
| Post Number: 5
|
The Hitchhiker
Unregistered
|
|
Posted on: Oct. 17 2004,04:05 |
|
|
!bodycode
If the bootloader doesn't find the ntldr, just think of the bootprocess step by step
1) cd-bootsector (Easyboot)
2) wxp or w2k bootsector (started by easyboot)
3) [cd]\i386\ntldr ...
so i think, you didn't replace the references in the wxp.bif and the w2k.bif from i386 to your new i386-directory
If found this page - and wit its help, i managed to create a 4 in 1 DVD
http://www.tech-hints.com
|
|
|
|
|
|
|
© 2002-2024 EZB Systems, Inc.
|
|
|
