It does say "setup was unable to copy the following file: c_1252.nls" I would say 1 out of every 5-7 it says that about. They are not being copied from a cd (it said there was no cdrom drivers installed) so Loupegarou (you can see his post on the previous page) gave me a way around it, and it was working except it skips some files. I didn't know if there is any way to go back and add the ones its skipping or not.
NTLDR is missing press Ctrl+Alt+Del to restart
- Thread starter Mindy
- Start date
- Status
Ah, ok.
One of the ways you can ensure that all the files are there (in your i386 folder on the hard drive) is to put your Windows CD into a working computer, go to My Computer, right click on the CD icon and go to "Open" or "Explore". Dig into the i386 folder and look at the status bar (may need to tick it in the view menu) to find out how many files there are.
Then go back and start the boot up process over on the broken computer (how you got to the windows setup screen), BUT before you type winnt to get to setup, do a DIR command from the black command prompt screen. It will list a bunch of files and then the totals (file count and file size) at the bottom. Don't worry about the names of the files unless you see weird non-English characters and blocks (a typical correct file name will be, for instance, shdocvw.dl_ - listed in the DIR command as SHDOCVW DLL - and a corrupt file name will be completely unreadable such as ¿Þïă®ţǿ ). If the number of files is wildly different or you see corrupt file names then something happened when copying the files to the hard drive.
Also, did you succeed in getting the drive to format as FAT32?
One of the ways you can ensure that all the files are there (in your i386 folder on the hard drive) is to put your Windows CD into a working computer, go to My Computer, right click on the CD icon and go to "Open" or "Explore". Dig into the i386 folder and look at the status bar (may need to tick it in the view menu) to find out how many files there are.
Then go back and start the boot up process over on the broken computer (how you got to the windows setup screen), BUT before you type winnt to get to setup, do a DIR command from the black command prompt screen. It will list a bunch of files and then the totals (file count and file size) at the bottom. Don't worry about the names of the files unless you see weird non-English characters and blocks (a typical correct file name will be, for instance, shdocvw.dl_ - listed in the DIR command as SHDOCVW DLL - and a corrupt file name will be completely unreadable such as ¿Þïă®ţǿ ). If the number of files is wildly different or you see corrupt file names then something happened when copying the files to the hard drive.
Also, did you succeed in getting the drive to format as FAT32?
lol yes after many hours of google searching, I was able to convert it... such a simple process I made very difficult. I could only convert 32gigs of it, I didn't know what to do with the rest so I just left it alone.
I will compare the number of files right now... thanks for helping me, this has been the longest most confusing process... I feel like I'm getting close to something, then something else comes up!
I will compare the number of files right now... thanks for helping me, this has been the longest most confusing process... I feel like I'm getting close to something, then something else comes up!
ok the i386 folder says 5398 files and the broken computers dir says 5390... but I think it's more than 8 files that aren't transfering.
BUT there are 8 folders in the i386 dir that contain even more files, perhaps it was those files that didn't copy? should that be the first thing I check?
BUT there are 8 folders in the i386 dir that contain even more files, perhaps it was those files that didn't copy? should that be the first thing I check?
Check to see if those folders are there in the i386 directory on the hard drive.
If I remember correctly this command lists all files without an extension (including directories/folders which the command will label as <DIR> before the file name instead of a file size)
DIR *.
Including the dot
edit: if that doesn't appear to show the folders, you can also try
DIR /O /P
(that's a letter o)
The /O will sort the file list, and the /P will have it prompt you to continue listing the files. Folders (also labeled with <DIR>) will be shown at the top of the list. To stop listing more pages, hold Ctrl and press C.
If I remember correctly this command lists all files without an extension (including directories/folders which the command will label as <DIR> before the file name instead of a file size)
DIR *.
Including the dot
edit: if that doesn't appear to show the folders, you can also try
DIR /O /P
(that's a letter o)
The /O will sort the file list, and the /P will have it prompt you to continue listing the files. Folders (also labeled with <DIR>) will be shown at the top of the list. To stop listing more pages, hold Ctrl and press C.
That's OK; to go one step further since you've got it in your good computer (booted up to Windows right?) then you can do this to check and see if it's all there, byte for byte:
Open two My Computer/Windows Explorer windows up and in one, go to the i386 folder on the broken computer's hard drive, then in the other, go to i386 on the setup CD.
Without selecting any files, right click on a blank area (might need to scroll to the end of the list to find a blank area big enough to hit) and select Properties. Do this for both of them. This will do a properties check on all of the files in the i386 folders. The CD will probably take longer to do than the hard drive. Move these property windows around so you can see them side by side
Once they are finished updating, then you can see the full count of all files and folders and exactly how much space it takes up. You will probably see two figures, one being "Size on disk:", which will likely be different than the other anyway. You want to compare the one above it that says "Size:", and the one that says "Contains:"
edit: oops. Looks like you already did that.
Alright, so now it sounds to me like it could be the hard drive going wonky.
Right click on the disk drive from my computer, then go to Properties. In Tools, start an error check. Don't check both checkboxes unless you want the scan to take a very long time; the scan for bad sectors (bottom checkbox) will literally scan every piece of the hard drive and see if it's suitable for writing/reading data.
However, if it does not find any errors in the initial scan then I think I'm out of ideas at the moment for why it could be failing to copy files.
Open two My Computer/Windows Explorer windows up and in one, go to the i386 folder on the broken computer's hard drive, then in the other, go to i386 on the setup CD.
Without selecting any files, right click on a blank area (might need to scroll to the end of the list to find a blank area big enough to hit) and select Properties. Do this for both of them. This will do a properties check on all of the files in the i386 folders. The CD will probably take longer to do than the hard drive. Move these property windows around so you can see them side by side
Once they are finished updating, then you can see the full count of all files and folders and exactly how much space it takes up. You will probably see two figures, one being "Size on disk:", which will likely be different than the other anyway. You want to compare the one above it that says "Size:", and the one that says "Contains:"
edit: oops. Looks like you already did that.
Alright, so now it sounds to me like it could be the hard drive going wonky.
Right click on the disk drive from my computer, then go to Properties. In Tools, start an error check. Don't check both checkboxes unless you want the scan to take a very long time; the scan for bad sectors (bottom checkbox) will literally scan every piece of the hard drive and see if it's suitable for writing/reading data.
However, if it does not find any errors in the initial scan then I think I'm out of ideas at the moment for why it could be failing to copy files.
Properties on the cd read: Type:File Folder, Location: E:\, Size: 460 MB (483,242,065 bytes), Size on disk: 467MB (490,184,704 bytes), Contains: 6415 Files, 113 Folders
Properties on the HD read: Type: File Folder, Location F:\, Size: 460 MB (483,242,065 bytes), Size on disk: 530 MB (556,007,424 bytes), Contains: 6415 Files, 113 Folders
Properties on the HD read: Type: File Folder, Location F:\, Size: 460 MB (483,242,065 bytes), Size on disk: 530 MB (556,007,424 bytes), Contains: 6415 Files, 113 Folders
Alright. Do an error check as outlined in the edit of my post just above... It might uncover some errors that may need to be repaired before the drive can be used. One of the disadvantages to FAT32 over NTFS is that it's far more likely to get errors in the file system, but you can't boot to a Win98 boot disk and be able to interact with an NTFS drive.
If you don't find anything in that error check and you're gonna give up for the night then let it do a bad sector check (check both checkboxes) while you sleep, because it will take a while.
I think I'm out of ideas up to this point. I should probably get to sleep myself :zzz:
If you don't find anything in that error check and you're gonna give up for the night then let it do a bad sector check (check both checkboxes) while you sleep, because it will take a while.
I think I'm out of ideas up to this point. I should probably get to sleep myself :zzz:
loupegarou
Posts: 39 +0
error
Mindy whenever i have gotten a couldnt copy file error it was one of two issues.
Primarily it has been bad memory.
Sometimes it could be a bad cdrom (disk or reader) or bad hard drive.
I dont understand how you didnt see the option to format with fat.
If you still want to try it with fat32 let me know. I will check back.
this should help you.
http://freepctech.com/pc/002/files010.shtml
Note 1:
A lot of people appear to be unaware of the fact that you do NOT need the 4, 5 or 6 setup disks in order to install Windows 2000 and XP. A common Win98 boot disk such as the Boot Disk Essentials diskette below can be used to install these OS's. This is what the Win XP System Setup Disk above does. Here's how to do it:
Start the computer with your chosen boot disk.
(MS Windows XP System setup disk) from their web page.
Change to the cdrom drive.
Go into the \i386 directory on the cdrom.
Run WINNT.EXE to begin the install process.
Mindy whenever i have gotten a couldnt copy file error it was one of two issues.
Primarily it has been bad memory.
Sometimes it could be a bad cdrom (disk or reader) or bad hard drive.
I dont understand how you didnt see the option to format with fat.
If you still want to try it with fat32 let me know. I will check back.
this should help you.
http://freepctech.com/pc/002/files010.shtml
Note 1:
A lot of people appear to be unaware of the fact that you do NOT need the 4, 5 or 6 setup disks in order to install Windows 2000 and XP. A common Win98 boot disk such as the Boot Disk Essentials diskette below can be used to install these OS's. This is what the Win XP System Setup Disk above does. Here's how to do it:
Start the computer with your chosen boot disk.
(MS Windows XP System setup disk) from their web page.
Change to the cdrom drive.
Go into the \i386 directory on the cdrom.
Run WINNT.EXE to begin the install process.
well i did it how you said the first time except instead of dragging the files from i386 I copied the whole folder INCLUDING the i386 folder (I did cd winXP last time, this time I did cd i386 after copying all the files that way) I don't know why it made a difference but it went through completely with no errors... still no luck, when I restarted it said "No Operating System Found". If I buy a new hard drive am I still going to have this problem?
computer help
Posts: 63 +0
I like the way some one asks for help then doesnt listen lol
heres something for you often people ask for help when you give it they dont listen anyway!!!
My advice leave this post alone !!!!!
heres something for you often people ask for help when you give it they dont listen anyway!!!My advice leave this post alone !!!!!
computer help
Posts: 63 +0
your not going to listen but anyway
with all these fantastic ideas its great people are trying to help one and another any how your missing file error relates to the master boot sector< MBR> of your hard drive !!!!
you need to create a new MBR first before installing cd !!!!!
delete your mbr and make a new one !!!! :slurp:
as ive said before if you have more than one hard drive and your main is a seagate you may need to use seagate drive intsaller !!!!
HOW EVER MAKE A NEW MBR FIRST
OR YOU WILL FAIL AND ALSO CHOOSE FULL FORMAT OR YOU WILL FAIL !!!
with all these fantastic ideas its great people are trying to help one and another any how your missing file error relates to the master boot sector< MBR> of your hard drive !!!!
you need to create a new MBR first before installing cd !!!!!
delete your mbr and make a new one !!!! :slurp:
as ive said before if you have more than one hard drive and your main is a seagate you may need to use seagate drive intsaller !!!!
HOW EVER MAKE A NEW MBR FIRST
OR YOU WILL FAIL AND ALSO CHOOSE FULL FORMAT OR YOU WILL FAIL !!!
I'm TRYING to listen, and have tried the listings that I understand... I'm sorry I'm not as computer literate as you, If I were I wouldn't need help. I don't know what it means to create a new MBR, I will look it up on the internet and try to figure it out. When I formatted I clicked quick format. When you say choose full format you mean to not check the quick option?
by the way when i get a message before the install starts that says "Setup did not detect SmartDrive on your computer. Smartdrive will greatly improve the performance of this phase of Windows Setup. Press F3 to exit Setup, or Press Enter to continue without Smartdrive." is that causing any problems even though the setup completes? Just a thought...probably a dumb one but a thought none the less
By the way Fury and Loupegarou thank you so so much for your patience, I have been able to wiggle my way through many computer problems but when it came to this I had absolutely no clue and you were very kind to walking me through everything, Thanks for taking the time...
Thanks to everyone who posted to help!
Thanks to everyone who posted to help!
loupegarou
Posts: 39 +0
cd rom issues
Well i would think you were having some issues with that rom.
What i would do is pull it out.
If you have a spare swap it to see if it shows up.
One other thing.
Hard drives and cdroms have jumpers on them.
The jumpers are what tell the bios/device if it is the primary drive or secondary.
Primary being master.
Secondary being slave.
the third option is cs (cable select).
If you have a grey cable coming off your motherboard and it has two places to plug ide devices into (two plastic things with holes (aprox 40=80 holes)) and you only have one of them filled with a cdrom or hard drive. You can set the jumpers to cable select (some motherboards dont like this) or you set them to master.
If you have two devices then one would be master (end of the cable) and one would be set to slave (closest to motherboard)
I hope this gets you working. Good luck Mindy. and no problem at all.
Well i would think you were having some issues with that rom.
What i would do is pull it out.
If you have a spare swap it to see if it shows up.
One other thing.
Hard drives and cdroms have jumpers on them.
The jumpers are what tell the bios/device if it is the primary drive or secondary.
Primary being master.
Secondary being slave.
the third option is cs (cable select).
If you have a grey cable coming off your motherboard and it has two places to plug ide devices into (two plastic things with holes (aprox 40=80 holes)) and you only have one of them filled with a cdrom or hard drive. You can set the jumpers to cable select (some motherboards dont like this) or you set them to master.
If you have two devices then one would be master (end of the cable) and one would be set to slave (closest to motherboard)
I hope this gets you working. Good luck Mindy. and no problem at all.
I pulled the cable to look at it, it has a slit in it! I don't know how or why but I replaced it with one of the ones from our dell (we have a dell and gateway that are here in pieces, thanks to your help I can probably get at least one of them running too, they had the same problem but instead of fixing it we bought 2 new ones lol)... any ways I put the new cable in and its working wonderfully. Thank you so so much for everything!
- Status
Latest posts
-
Worry your friends with this $9,420 flamethrower robot dog
- Tinderbox replied
-
Researchers have unlocked the "Holy Grail" of memory technology- DanteSmith replied
