win 2003 standard edition: failed installation

[oupei]

Hi, I got windows 2003 SE from MSDNAA for research purposes. I'm trying to install it, but it's not working. The install process goes through without a hitch, but when I try to boot it up, it says that ntoskrnl.exe is missing. I googled that, and it turns out that I can copy that manually from the CD, so I do. But when I try again, it tells me that HAL.dll is missing. So I copy that over and more files are missing.

I've tried installing a couple times but it all results in the exact same situation. Anybody know what to do?

 

[jamesbond007]

Is this a new box? If so, check your IDE/SATA connections on the optical drive and the HDD. Is your PSU adequate enough? (enough juice for your system) I've seen a bad/weak PSU cause a LOT of strange errors.

If your CPU is overclocked, clock it back to normal. Also, run Memtest and make sure your RAM is all good. I personally like the bootable CD image available. When you are formatting the drive during the Windows setup, instead of a quick, do a full format. I think it just says 'Format to NFTS'. Choose the option sans 'quick' and that should do it.

That should give you a start. Good luck!

 

[Genx87]

First thing I would do is find out if you are booting off a HD attached to a SATA or SCSI controller. If you are then you will need to install the drivers at the beginning of the install process.

 

[jamesbond007]

Originally posted by: Genx87
First thing I would do is find out if you are booting off a HD attached to a SATA or SCSI controller. If you are then you will need to install the drivers at the beginning of the install process.

If that were the case, I doubt he'd be able to finish, let alone start, the copying process since the Windows installer wouldn't be able to access the harddisk that was on a controller of that nature.

 

[spyordie007]

Originally posted by: jamesbond007

Originally posted by: Genx87
First thing I would do is find out if you are booting off a HD attached to a SATA or SCSI controller. If you are then you will need to install the drivers at the beginning of the install process.

If that were the case, I doubt he'd be able to finish, let alone start, the copying process since the Windows installer wouldn't be able to access the harddisk that was on a controller of that nature.

Not neccisarily. I've seen cases where it's able to copy the files but is unable to boot afterwards (innacessible boot device). Although this is uncommon, generally if the drivers are not present it wont show the drive(s) at all.

I agree with your post earlier that the hardware should be looked at first as it is the most likely culprit.

 

[jamesbond007]

spyordie007, nice nick.

Anyways, what motherboard/controller would give such an instance? I'm not doubting you, but hands-on experience is priceless and I would like to know for future reference.

Thanks!

 

[spyordie007]

Nice handle there james

As I try and remember when I think the only installs that I've had that issue with were SCSI RAID controllers. I dont recall what exact hardware though (most likely PERC). My guess would be that the "generic" SCSI drivers on the Windows CD was enough to copy the files but not to boot. In all of the cases I've seen it the install never got further than the first boot after copying the files, the installs were never able to actually complete.

Erik

 

[Smilin]

missing ntoskrnl in this case is likely arc path related and not related to the actual file missing.

Do this:
Boot to recovery console (you'll have to provide F6 drivers during setup boot).

Run:
map arc

Run:
type c:\boot.ini

Compare the two outputs and see what's wrong.

 

[jamesbond007]

Originally posted by: spyordie007
Nice handle there james

As I try and remember when I think the only installs that I've had that issue with were SCSI RAID controllers. I dont recall what exact hardware though (most likely PERC). My guess would be that the "generic" SCSI drivers on the Windows CD was enough to copy the files but not to boot. In all of the cases I've seen it the install never got further than the first boot after copying the files, the installs were never able to actually complete.

Erik

Sounds like a case of trial and error, first time round! I try to always install the drivers off the disk (hardware disk) rather than let Windows try it's run at getting things right. In any case, at least you just had to reboot, put the drivers in, and restart the install!

 

[Brazen]

Originally posted by: oupei
Hi, I got windows 2003 SE from MSDNAA for research purposes. I'm trying to install it, but it's not working. The install process goes through without a hitch, but when I try to boot it up, it says that ntoskrnl.exe is missing. I googled that, and it turns out that I can copy that manually from the CD, so I do. But when I try again, it tells me that HAL.dll is missing. So I copy that over and more files are missing.

I've tried installing a couple times but it all results in the exact same situation. Anybody know what to do?

Sounds like you picked a bad torrent.

If you are really just wanting it for research, you can get the free eval from Microsoft here.

Either way it sounds like you have a bad disc. Let me offer you this anecdote:

At work, we get the volume licensing packs every month from Microsoft. Now, the fact is, good CDs can go bad (by getting scratched or whatever), so first thing I do is make an ISO of any Microsoft CDs that we use and then NEVER use the originals (they go in storage for safe keeping). I do a lot of test-installs in our lab and throw the CDs around a lot and I'll sometimes get the EXACT same thing you are talking about. I've found that burning a new CD from the ISO fixes this. I've also found, that on my work's cheapo cd burner, if I burn at the max speed I get these same errors. On that particular burner, it is best to set the burn speed lower (8X for this burner) and then I don't have that problem.

(edit: btw, I make ISO copies of ANY cd's that we use, Microsoft or anyone else).

 

[oupei]

Hey everybody. I'm back. Dang I didn't expect so many replies in just a couple days. ok, Lemme see...

007, 87, and other 007: you guys are pointing to hardware. This install is on my winxp box that runs xp32bit fine. It is not OCed. Here's the details:

A64 2800+ newcastle s754
Epox EP-8KDA3I
Antec 1650 Case and included PSU
PNY GF6800 NU
2x1GB PC3200 OZC Valueram

I doubt that it is hardware for a few reasons. Firstly, winxp installs and runs fine. Second, I can manually copy over the missing files and they will be there. That means the hard disk is writing fine. The only possibility is that maybe the CPU doesn't run the installation correctly and skips the necessary files. I've formated the hard drive, but I'll do it again just to be sure.



smilin: you suggest the path, but I don't think this is the case either because if I manually copy the file over, it will detect the file I copied.

brazen: you point to the cd. It's quite possible because I had to pick up this cd from my university's MSDNAA department, instead of downloading it like the other MSDNAA software we get. I have copied an ISO onto my harddrive and it didn't detect any unfixable CRC errors. I'll try burning a copy, but if there's a problem with the original, then the copy will probably have a problem too. Are the eval CDs exactly the same as regular CDs (with the key determining whether it is eval or not)? that would help eliminate this as a factor.

Thanks everybody, I really appreciate your input. Here's what I'm going to try:
1. full format the hard drive
2. burn new cd from image
3. try the install again, but this time with the winxp hard drive removed
4. if it doesn't work, try the map arc thing

I'll let you guys know if it works.

edit: I also have a spare winxp64bit that I could try installing. would that eliminate any possible culprits?

 

[Smilin]

"smilin: you suggest the path, but I don't think this is the case either because if I manually copy the file over, it will detect the file I copied."

Perhaps because you are dropping the copied file into the path where it is looking?

The steps I outlined simply tell you if it's looking in the right place. It only takes a couple min to run a "map arc". Definately worth the data collection time when troubleshooting a missing boot file problem. Spend the 5min doing this before you spend half an hour reloading.

 

[ebaycj]

I've gotten this error with bad memory, I've also seen it with a bad cd-rom drive. I would imagine that bad cabling could do it as well. Either that or you are actually missing the files.