AMD Radeon Adrenalin release date, new features, compatible graphics cards
biggg helllp pls. my brother instaled norton, it restarted but message came up cannot find system, something to do with ntldr. is this to do with re-booting, everything is in dos and both of us are cluless.
any advise greatyl appreciated.
ty verymuch will try it and let u know.
Just had a look at the ref. I gave. It doesn't look very helpful.
As the error was conected with Norton, have a look at the Norton Website. There may be something better there.
If you have a floppy disk in your drive take it out and then your machine off and then back on again.
Type ntldr into "Google" it brings up a few hits.
ntldr is a system file used in NT, 2000, XP.
It is normally invisible (sys file).
The mbr (master boot record)starts the ntldr program. This looks at the bootini file to find the operating system. ntldr then calls ntdetect to see if NT/2000/XP is present. ntldr then loads it (or selects the other operating system (if detected).
The ntldr file could and should be copied by everyone onto a backup floppy or seperate folder along with the other 2 files mentioned above.
They should be in c:\ root directory.
Wot to do?
1. Hold F8 when booting, Select "Last Known Good Config" from menu. If not recoverd try 2.
2. As above but select "Safe mode with command"
and run attrib to see if files are present in c:\.
If not: do 3.
3. Run the install program from the operating system CD and select "Repair", read the options, it does not wipe the whole disk, only re-copies the op system, but of course that depends on how much has been destryoed/lost/changed already.
Ensure no other program is running (especially virus protector) when you re-install Norton.
Tell us wot op system pls for more details and help.
Don't use the sys c: command. It will only copy the 98 boot files to your C drive, and turn the XP boot sector into a 98 boot sector.
If the error message is "ntldr is missing", the more common cause is something went wrong with the boot path in the boot.ini file, so that although the file is there, Windows is looking in the wrong place for the file. Reason why boot.ini has gone wrong is unclear.
I assume you're using XP? Try re-creating the boot.ini file.
Boot up the computer with the XP CD, and press R to go into the Recovery Console. Select your XP installation (usually it's number 1). so press 1 and press enter. Enter your administrator password.
At the C:>WINDOWS prompt, type map and press Enter. This will show the drive letters on your computer. Note the drive letter for your CDROM.
At the prompt, type:
copy x:\i386\ntldr c: and press Enter, where x is the drive letter of your CDROM (probably d). If you are asked whether to overwrite the file, it means you already have it and it's not missing, but say yes anyway, so press y and Enter.
At the prompt, type:
copy x:\i386\ntdetect.com c: and press Enter. Say yes again if prompted.
Then to re-create the boot.ini file, at the C:\WINDOWS> prompt again, type:
and press Enter.
Recovery Console will then scan your computer for XP installations, and prompt you to provide further details.
When asked whether to add an XP installation to the boot list, say yes.
When asked to enter Load Identifier, just type:
Windows XP Home
and press Enter (or Professional, as the case may be).
When asked to enter the Operating System Load Option, type
and press Enter.
When this is all done, back at the C:\WINDOWS> prompt, type exit and press Enter. Computer will restart. Remove XP CD, and see if it can boot into XP.
Note that if you have used the sys c: command after booting up from a DOS or 98 boot floppy, you need to take an extra step in XP Recovery Console. This is because the sys C: command would have copied the DOS or 98 boot files to your C drive and changed the boot sector to a DOS or 98 bootsector. Your computer would not be looking for the XP boot files even if they were all there.
So if you did use the sys c: command, in Recovery Console, before your type exit, do the following. At the C:\WINDOWS> prompt, type:
and press Enter. Confirm what you want to do. Then exit Recovery Console to reboot.
Hope it works.
This thread is now locked and can not be replied to.