|
|
| Post Number: 1
|
Limerick 
Group: Members
Posts: 25
Joined: Apr. 2005
|
 |
Posted on: Apr. 10 2005,08:33 |
|
   |
Hello all,
Here I am... again...
I followed the help file to include a XP Home installation file in my EZB CD, but when choosing to install with my EZB menu, I've a message saying : "Could Not Find NTLDR"
But I checked this file is in the I386 folder (setupldr.bin and bootfix.bin). And both win51 and win51ic are also in C:\EasyBoot\disk1
Where should I put this NTLDR file ?
--------------
Lim.
|
 |
|
|
| Post Number: 2
|
eureka
Unregistered
|
 |
Posted on: Apr. 10 2005,12:33 |
|
 |
Hello again Limerick
Ntldr should reside in i386 and is only used for Windows when initiating its start procedure.
Some briefing about NTLDR: NTLDR is a program loaded from the hard drive boot sector that displays the Microsoft Windows NT startup menu and helps Microsoft Windows NT load.
I suppose the first part (copy files) is working and when finished with this, computer reboots, and you get this message: "Could Not Find NTLDR". Am I right? If this is the case, copy a new NTLDR file to EasyBoot\disk1\i386-folder to be sure that this file isn’t corrupt (happens to me sometimes).
eureka
|
|
|
|
| Post Number: 3
|
eureka
Unregistered
|
 |
Posted on: Apr. 10 2005,13:15 |
|
|
Limerick, I’m not sure how you tested this install.
I can tell you this, that often a user will see the message "NTLDR is Missing" after attempting to install Windows 2000 or Windows XP, or upgrade a Windows 95-based or Windows 98-based computer to Windows 2000 or Windows XP. The message appears after the first reboot. This occurs only if Windows 95 or 98 has been installed on a drive with the FAT32 file system.
To correct the problem, the user must boot the computer with a Windows 95 or 98 Startup diskette or another bootable diskette with sys.com on it. Then, at the "A:\>" prompt, type "sys c:" and press "enter." A "System Transferred" prompt should appear and then the user must reboot the computer without the diskette.
But if you make a “clean install” (with a formatted hard disk) this problem shouldn’t appear.
eureka
|
|
|
|
| Post Number: 4
|
Limerick
Group: Members
Posts: 25
Joined: Apr. 2005
|
|
Posted on: Apr. 10 2005,13:20 |
|
|
| Quote (Guest @ April 10 2005,18:33) | | I suppose the first part (copy files) is working and when finished with this, computer reboots, and you get this message: "Could Not Find NTLDR".  Am I right? If this is the case, copy a new NTLDR file to EasyBoot\disk1\i386-folder to be sure that this file isn’t corrupt (happens to me sometimes). |
Not exactly eureka.
I boot with EZB, want to launch the XP install by clicking on the menu (command run w2ksect.bin) and have directly the "Could Not Find NTLDR".
As I previously said, the NTLDR file is in the I386 folder.
--------------
Lim.
|
|
|
|
| Post Number: 5
|
eureka
Unregistered
|
|
Posted on: Apr. 10 2005,13:51 |
|
|
Hello Limerick
To clear things up…
Basically it should look like this:
EasyBoot\disk1
win51
win51ic
i386
then
EasyBoot\disk1\ezboot\ w2ksect.bin (and other ezb files and images)
i386 should reside on root (easyBoot\disk1) together with win51, win51c
w2ksect.bin should be in ezboot folder.
Must point out that this is another mysterious problem, because w2ksect.bin points to setupldr in i386 folder witch then starts up installation procedure. Now it seems to point to the root and ntldr.bin file.
Make sure to only use the option “optimise” when creating ISO file.
eureka
|
|
|
|
| Post Number: 6
|
Limerick
Group: Members
Posts: 25
Joined: Apr. 2005
|
|
Posted on: Apr. 10 2005,16:35 |
|
|
Ok, I progress.
I can boot on EZB and when selecting "Install XP", it begins to run but ask to insert a Floppy (?) containing XP.
But all files are on the EZB CD-Rom, so it would be enough...
--------------
Lim.
|
|
|
|
| Post Number: 7
|
eureka
Unregistered
|
|
Posted on: Apr. 10 2005,17:09 |
|
|
Limerick….
I am sorry, if my suggestion was not exactly what you wanted. Sometimes, there are 20 ways of doing things, especially with M$ products, and none of them are what you want to do!!!
However, it begins to run but ask to insert a Floppy. You get this message when some of win51 files is missing on the root (Easyboot\disk1) or you have wrong types of win51 files. Depending on XP version there should be different win51 files.
Note: If using winXP_pro with slipstreamed sp2 you have to insert new (different) win51 files to the root (yes I have noticed that this issue of yours only concerns winXP_home – only want to point it out anyway).
Make sure you have the right stuff according to what version of integrated servicepack you are dealing with (if this have been done with installation files in i386).
Seems that the installation program can’t find win51 and win51ic on root (EasyBoot\disk1). Or there should be new (different) files according to some upgrade. I really don’t now.
At least you have come one step further (no NTLDR missing any more).
eureka
|
|
|
|
| Post Number: 8
|
Limerick
Group: Members
Posts: 25
Joined: Apr. 2005
|
|
Posted on: Apr. 10 2005,17:32 |
|
|
eureka, don't be sorry.
It's very kind from you to help me the way you do 
I did put the two Win51 files (win51 and win51ic) in EasyBoot\disk1
The "master" of XP is the Dell XP Home SP2 provided with the laptop and which I've "nLited".
This XP nLited install works as I managed to install it on the Laptop.
What I want to do, is now to implement this "nLited" XP install to my EasyBoot CD on which there are already my 2 Acronis tools.
And then I could give to my father this All-In-One CD in case of problem.
On this CD, there would be :
- the 2 Acronis tools,
- Drive Fitness Test (his previous laptop failed due to HDD death)
- "nLited" XP Home SP2
From now, every thing run (or should) except this XP install.
These explanations may help you to understand what I intend to do exactly.
I should have told you this before, sorry  
Have a good night,
Edited by Limerick on Apr. 10 2005,17:33
--------------
Lim.
|
|
|
|
| Post Number: 9
|
eureka
Unregistered
|
|
Posted on: Apr. 11 2005,02:26 |
|
|
Limerick
Please do this step bye step.
1. Start with installing this “Nlite-version” of WinXP-home on a different computer. (Note: use a “clean” CD without integrating it to EasyBoot).
2. If it fails, use original (“Master”) Dell XP-home CD (no Nlite) on that “different computer”. If this run as supposed, well then the problem is Nlite (common problem – I can tell you that!).
3. If even step 2 fails, you have a sample of Dell CD that’s been “hacked” to only install on that motherboard that belongs to your original Dell Laptop.
Yes I have experiences that point in this direction. Maybe not this one, but must be sorted out thru this step bye step test.
Why not use “Virtuell Pc” from Microsoft? It’s possible to test both ISO file made bye EasyBoot and/or run original CD from CD-unit. No need for burning CD every “test cycle”.
eureka
|
|
|
|
| Post Number: 10
|
Limerick
Group: Members
Posts: 25
Joined: Apr. 2005
|
|
Posted on: Apr. 11 2005,14:34 |
|
|
Hello eureka,
1. It works without any problem
2. As it did not fail, I did not try
3. I did not try also.
So the problem seems to come from the integration of my XP install (nLited or not) into EasyBoot.
There is something I might do wrong...
--------------
Lim.
|
|
|
|
|
|
|
© 2002-2024 EZB Systems, Inc.
|
|
|
