Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account


Photo

win2k + uSP5.1 + nLite = error


  • Please log in to reply
7 replies to this topic

#1
Matt Cauldrin

Matt Cauldrin
  • Members
  • 3 posts
I have tryed to slipstream uSP5.1 onto OEM Win2k SP0 with nLite
it installed (Ithink -Ididnt watch it) on reboot I get this :

Boot from ATPI CD-rom:
Press any Key .....j

and things stop .
Is the ' j ' and error code ..What's it mean?

thanks :)

[edit] when no CD in drive :

Boot from ATPI CD-ROM: Failure....
j


and booting sequence stops :(

Edited by Matt Cauldrin, 22 April 2006 - 09:01 PM.



How to remove advertisement from MSFN

#2
xpmaniac4ever

xpmaniac4ever

    We would change the world if God would give us the sourcecode

  • Members
  • PipPip
  • 136 posts
Man, did you check your boot order in BIOS ? Make sure you are able to boot from harddisk after CDROM.

Edited by xpmaniac4ever, 23 April 2006 - 01:27 AM.


#3
Dels

Dels

    X2K Project Leader

  • Members
  • PipPipPip
  • 332 posts
i use usp51 slipstreamed win2k cd with nlite and i don't have any bug, if the boot order is correct try to remake your windows custom source

#4
Matt Cauldrin

Matt Cauldrin
  • Members
  • 3 posts
boot order is correct

watched the install process and it is give the problem when the PC tries to reboot after transfering the the files to the hard drive

Boot from ATPI CD-rom:
Press any Key .....j

redownloaded uSP5.1 - checked the hash ,Made a couple more CDs , no joy :realmad:

I tryied the original genuine Win2k cd same thing :(

try a Xp CD got this stop error when rebooting after files transfer

STOP: c0000221 unknown hard error
\SystemRoot\system32\ntdll.dll


Must be broken HDD ?? do you think ??

Edited by Matt Cauldrin, 24 April 2006 - 04:17 AM.


#5
Matt Cauldrin

Matt Cauldrin
  • Members
  • 3 posts
hmmm.. well i swaped the HD and :thumbup

but I don't understand how could the drive format ok and still be bad ?
especially WinXp formats the drive and then check its ok hmm.. :huh: :(

#6
-I-

-I-

    win2k Freak

  • Members
  • PipPipPipPip
  • 639 posts
try low-level formating the disk ...
most hdisk manufactors have a tools disk for such operations...

Search @ Google = low level format <insert hddrive name here>

#7
Electrician

Electrician

    Member

  • Members
  • PipPip
  • 113 posts
  • OS:XP Pro x86
  • Country: Country Flag
I had the same problem once. Win 2k would go through and format the drive, copy files to it, reboot and
#!* the drive was bad! Even tried powerquest tool to reformat the drive, but same process.
Tried another drive (a small klunker I had lying around) SAME problem.
SO, I started over on original drive, with a diff motherboard. Format, copy files reboot <shut off and put drive on problem MOBO> boot, windows installed just fine.
I chalked it up to something flakey with the AMD chipset.

Was doing a re-install for a friend and was p***ed at my wasted time, so no more chance or attempts to test it further.

BTW XP uses a slightly diff NTFS format than 2k.

#8
DanceMan

DanceMan

    Newbie

  • Members
  • 18 posts
Windows installs can go pear shaped from various hardware issues. Since installs are often prompted by some kind of problem or failure, it's generally a good idea to run two simple tests before proceeding: the hard drive manufacturer's test utility and memtest86+ for the ram. Both of these will run from a self booting floppy, and thus require no working OS in the computer. If you lack a floppy, the Ultimate Boot CD contains all the hdd utiilities and memtest.




1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users



How to remove advertisement from MSFN