Link to home
Create AccountLog in
Avatar of jackdia
jackdia

asked on

booting up recieve window/can't find system32/l_intl.nls

"WINDOWS\System32\l_Intl.nls is missing or corrupt" message on boot. It says to put the system disk in (did)

(XP Pro) and hit repair. Did  This is an IBM T30 2366 series.  If I load of the Ibm repair disk Ill lose any date   have any ideas?  

 bye the way this is my first time here. So Hello From Napa Ca.  I have to move it two days

One of the answers if found the link doesnt workwas from:
bluepointx:
I have one.

Download NTFSDOS which will allow you full read/write capabilites with a bootable diskette. You can download it from here:

http://www.sysinternals.com/Utilities/NtfsDos.html

Create the bootable floppy using that program, then copy the needed file on that floppy too. After you boot up using that floppy, you will be able to navigate through the hard drive and you will be able to put that file where it belongs. Thus enabling you to boot up your XP.
ASKER CERTIFIED SOLUTION
Avatar of stevenb01
stevenb01

Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
Avatar of mikelfritz
Boot from your XP CD, and press R to goto the recovery console, choose the installation that is not working from the list and enter the administrator password when prompted.

at the command prompt

type exactly. (where D: is your CDrom drive letter, it may be diffrent)


expand D:\i386\L_INTL.NL_ c:\Windows\system32\L_INTL.NLS

answer yes to any overwite prompt
Avatar of jackdia
jackdia

ASKER


mikelfritz:
After changing from C:windows to D: I typed

expand D:\i386\L_INTL.NL_ c:\Windows\system32\L_INTL.NLS

Received

The file name, directory name, or volume label syntax is incorrect
Avatar of jackdia

ASKER

My Mistake the drive need use was E not D I get Access is denied.
Try to just use copy (I think expand may not work in Rconsole - it will still expand though)
copy e:\i386\L_INTL.NL_  c:\Windows\system32\L_INTL.NLS
There is most likely a copy under "c:\windows\servicepackfiles\i386" as well, so:

copy c:\windows\servicepackfiles\i386\L_INTL.NLS c:\Windows\system32\L_INTL.NLS

Avatar of jackdia

ASKER

Returns
The system cannot find the file specified
Avatar of jackdia

ASKER

copy e:\i386\L_INTL.NL_  c:\Windows\system32\L_INTL.NLS

returns

the system cannot find the file or directory specified
do a search on another pc for  L_INTL.NLS, and copy it to a floppy, or ram stick, then copy it to your pc at the correct location
Avatar of jackdia

ASKER

good idea tried
returns
the file could not me copeid.
 
7046 l_intl.nls

then you must copy it when you are not booted from that disk; use bartpe or knoppix to boot, then copy the file :
ftp://ftp.uni-kl.de/pub/linux/knoppix/KNOPPIX_V5.1.0CD-2006-12-30-EN.iso      Knoppix      
www.nu2.nu/pebuilder/                                     BartPe

this can also be ussed :  unstoppable copier
http://www.roadkil.net/unstopcp.html
Your  attrib -R option is good .. but do keep in mind the copy or expand command does not give you what side of the copy is failing.. (eg cannot access ram drive or cd vs cannot write to c:\windows\system32...)
Another thing to consider is the fact you logged on to the recovery console using local admin credentials so it really shouldnt be a "permissions" issue..
Quite a bit of the time a +r file credential that cannot be changed, or a directory that cannot be written to is caused by file allocation issues or a hard drive issue... My suggestion is to run a chkdsk /r from recovery console to fix it.. as it did in my case of missing l_intl.nls....
May not be a bad idea to run hardware diags to test your hard drives out as well...
I did not take nobus'es way but would more than likley work as well if you are comfortable in the linux world. I for one am,, but didnt need to..