STOP: c0000218

  • Thread starter Thread starter Jon
  • Start date Start date
J

Jon

From a cold startup my Windows 2000 system starts to bootup. It gets to the graphical windows 2000 start up screen (the white blocks get right to the end) just before the GUI appears and it reboots. It does this 3 times and then goes into Windows normally. A blue screen briefly appears with the following information before it reboots:

STOP: c0000218 (registry file failure)
The Registry cannot load the hive (file):
\systemRoot\System32\config\SOFTWARE
or it's log or alternate.
It is corrupt, absent or not writable
Beginning dump of physical memory
Physical memory dump complete.
Contact your system technical support group.


When I finally get into Windows The event log has recorded the following:

The computer has rebooted from a bugcheck. The bugcheck was: 0xc0000218 (0xe166e148, 0x00000000, 0x00000000, 0x00000000). Microsoft Windows 2000 [v15.2195]. A dump was saved in: C:\WINNT\Minidump\Mini010405-01.dmp.
Any ideas what this might be to do with?

It always happens each day on a cold startup. It doesn't tend to happen if I reboot it whilst it's been on for a while.

Any ideas what might be causing this?
 
Jon said:
From a cold startup my Windows 2000 system starts to bootup. It gets
to the graphical windows 2000 start up screen (the white blocks get
right to the end) just before the GUI appears and it reboots. It does
this 3 times and then goes into Windows normally. A blue screen
briefly appears with the following information before it reboots:

STOP: c0000218 (registry file failure)
The Registry cannot load the hive (file):
\systemRoot\System32\config\SOFTWARE
or it's log or alternate.
It is corrupt, absent or not writable
Beginning dump of physical memory
Physical memory dump complete.
Contact your system technical support group.


When I finally get into Windows The event log has recorded the
following:

The computer has rebooted from a bugcheck. The bugcheck was:
0xc0000218 (0xe166e148, 0x00000000, 0x00000000, 0x00000000). Microsoft
Windows 2000 [v15.2195]. A dump was saved in:
C:\WINNT\Minidump\Mini010405-01.dmp. Any ideas what this might be to
do with?

It always happens each day on a cold startup. It doesn't tend to
happen if I reboot it whilst it's been on for a while.

Any ideas what might be causing this?
------=_NextPart_000_0010_01C4F2AA.CEF54880
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html;
charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1476" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff background="">
<DIV><FONT face=Arial size=2>From a cold startup my Windows 2000
system starts
to bootup.&nbsp; It gets to the graphical windows 2000 start up screen
(the white blocks get right to the end) just before the GUI appears
and it reboots.&nbsp; It does this 3 times and then goes into Windows
normally.&nbsp; A blue screen briefly appears with the following
information before it reboots:<BR><BR><FONT color=#0000ff>STOP:
c0000218 (registry file failure)
<BR>The Registry cannot load the hive
(file):<BR>\systemRoot\System32\config\SOFTWARE<BR>or it's log or
alternate.<BR>It is corrupt, absent or not writable<BR>Beginning dump
of physical memory<BR>Physical memory dump complete.<BR>Contact your
system technical support group.</FONT></FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2></FONT><FONT face=Arial
size=2></FONT><BR><FONT
face=Arial size=2>When I finally get into Windows The event log has
recorded the following:</FONT></DIV><FONT face=Arial size=2>
<DIV><BR>The computer has rebooted from a bugcheck. The bugcheck was:
0xc0000218
(0xe166e148, 0x00000000, 0x00000000, 0x00000000). Microsoft Windows
2000 [v15.2195]. A dump was saved in:
C:\WINNT\Minidump\Mini010405-01.dmp. <BR>Any ideas what this might be
to do with?</DIV>
<DIV>&nbsp;</DIV>
<DIV>It always happens each day on a cold startup.&nbsp; It doesn't
tend
to
happen if I reboot it whilst it's been on for a while.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Any ideas what might be causing this?</FONT></DIV></BODY></HTML>

------=_NextPart_000_0010_01C4F2AA.CEF54880--
Click to expand...

Since you say it happens on a cold boot only it sounds like it is a
drive or controller problem. I would not expect it to be controller
though because it would not be so consistent. I would run a thorough
chkdsk. Goto a CMD prompt and run chkdsk /r. Answer yes to running it on
the next reboot. I suspect it will find a media defect on the drive. It
may fix the problem short term but I expect you to have additional
problems with the drive until it fails.

Leonard Severt
Microsoft Enterprise Support
 
Sounds like some hardware failure.

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
From a cold startup my Windows 2000 system starts to bootup. It gets to the
graphical windows 2000 start up screen (the white blocks get right to the
end) just before the GUI appears and it reboots. It does this 3 times and
then goes into Windows normally. A blue screen briefly appears with the
following information before it reboots:

STOP: c0000218 (registry file failure)
The Registry cannot load the hive (file):
\systemRoot\System32\config\SOFTWARE
or it's log or alternate.
It is corrupt, absent or not writable
Beginning dump of physical memory
Physical memory dump complete.
Contact your system technical support group.


When I finally get into Windows The event log has recorded the following:

The computer has rebooted from a bugcheck. The bugcheck was: 0xc0000218
(0xe166e148, 0x00000000, 0x00000000, 0x00000000). Microsoft Windows 2000
[v15.2195]. A dump was saved in: C:\WINNT\Minidump\Mini010405-01.dmp.
Any ideas what this might be to do with?

It always happens each day on a cold startup. It doesn't tend to happen if
I reboot it whilst it's been on for a while.

Any ideas what might be causing this?
 
In said:
From a cold startup my Windows 2000 system starts to bootup. It
gets to the graphical windows 2000 start up screen (the white
blocks get right to the end) just before the GUI appears and it
reboots. It does this 3 times and then goes into Windows
normally. A blue screen briefly appears with the following
information before it reboots:

STOP: c0000218 (registry file failure)
The Registry cannot load the hive (file):
\systemRoot\System32\config\SOFTWARE
or it's log or alternate.
It is corrupt, absent or not writable
Beginning dump of physical memory
Physical memory dump complete.
Contact your system technical support group.


When I finally get into Windows The event log has recorded the
following:

The computer has rebooted from a bugcheck. The bugcheck was:
0xc0000218 (0xe166e148, 0x00000000, 0x00000000, 0x00000000).
Microsoft Windows 2000 [v15.2195]. A dump was saved in:
C:\WINNT\Minidump\Mini010405-01.dmp. Any ideas what this might be
to do with?

It always happens each day on a cold startup. It doesn't tend to
happen if I reboot it whilst it's been on for a while.

Any ideas what might be causing this?
Click to expand...
[ ]

Since you say it happens on a cold boot only it sounds like it is
a drive or controller problem. I would not expect it to be
controller though because it would not be so consistent. I would
run a thorough chkdsk. Goto a CMD prompt and run chkdsk /r. Answer
yes to running it on the next reboot. I suspect it will find a
media defect on the drive. It may fix the problem short term but I
expect you to have additional problems with the drive until it
fails.
Click to expand...

Beyond CHKDSK one might get the HD manufacturer's diagnostics
(bootable diskette) and run them on a "cold" drive. Could be
revealing.

In any case this does seem to have a hardware factor involved, be it
HD or something else. Any Event Log entries?
 
I'm getting the same error. Doesn't matter if system cold boots or reboots
when warm. Ran chkdsk /r and found and fixed some errors. Ran it again and no
errors found. Appears to be a corrupt registry issue. Any ideas?
 
ran chkdsk /r -no problems reported. Worth trying winidows 2000's registry
repair util?

see if that fixes it for you?

http://www.microsoft.com/downloads/...01-2c68-4de8-9229-ca494362419c&displaylang=en


JohnS said:
I'm getting the same error. Doesn't matter if system cold boots or reboots
when warm. Ran chkdsk /r and found and fixed some errors. Ran it again and no
errors found. Appears to be a corrupt registry issue. Any ideas?
Click to expand...
the graphical windows 2000 start up screen (the white blocks get right to
the end) just before the GUI appears and it reboots. It does this 3 times
and then goes into Windows normally. A blue screen briefly appears with the
following information before it reboots:(0xe166e148, 0x00000000, 0x00000000, 0x00000000). Microsoft Windows 2000
[v15.2195]. A dump was saved in: C:\WINNT\Minidump\Mini010405-01.dmp.
 
I'm getting the same error. Doesn't matter if system cold boots or
reboots when warm. Ran chkdsk /r and found and fixed some errors. Ran
it again and no errors found. Appears to be a corrupt registry issue.
Any ideas?

Jon said:
From a cold startup my Windows 2000 system starts to bootup. It gets
to the graphical windows 2000 start up screen (the white blocks get
right to the end) just before the GUI appears and it reboots. It
does this 3 times and then goes into Windows normally. A blue screen
briefly appears with the following information before it reboots:

STOP: c0000218 (registry file failure)
The Registry cannot load the hive (file):
\systemRoot\System32\config\SOFTWARE
or it's log or alternate.
It is corrupt, absent or not writable
Beginning dump of physical memory
Physical memory dump complete.
Contact your system technical support group.


When I finally get into Windows The event log has recorded the
following:

The computer has rebooted from a bugcheck. The bugcheck was:
0xc0000218 (0xe166e148, 0x00000000, 0x00000000, 0x00000000).
Microsoft Windows 2000 [v15.2195]. A dump was saved in:
C:\WINNT\Minidump\Mini010405-01.dmp. Any ideas what this might be to
do with?

It always happens each day on a cold startup. It doesn't tend to
happen if I reboot it whilst it's been on for a while.

Any ideas what might be causing this?
Click to expand...
Click to expand...

When you have a corrupt registry there are 2 ways to fix it.

1. Use the chkreg utility.
http://www.microsoft.com/downloads/details.aspx?FamilyID=56d3c201-2c68-
4de8-9229-ca494362419c&displaylang=en

Follow the instructions with it to make the boot disk which will then
automatically run it.

2. Copy a backup of the registry hive in recovery console. In the
Windows\repair folder you will find the original registry hives that
were created at the time Windows was installed. In addition if you have
ever made an ERD or a system state backup with NTBackup there will be a
regback folder under repair that will contain the more recent copies of
the registry that were saved at that time.

Boot to recovery console
Check the windows\repair folder to see if you have a regback folder
Change to the windows\system32\config folder (this is where the live
registry is stored)
Rename which every registry hive has the problem (software, system, etc)
Copy the registry hive from either windows\repair or windows\repair
\regback.

One of these methods will work. I would try chkreg first.

Leonard Severt
Microsoft Enterprise Support
 
If the software hive is corrupt, it may be possible to rename the software
hive found in;
%windir%\system32\config\software
to software.old
then copy the most recent backup found in
%windir%\repair\regback
as
%windir%\system32\config\software

If that fails you can copy/ use the file
%windir%\repair\software
This file is an image of the hive at the time the OS was installed, so you'd
have to reinstall all software. This being the case you might just as well
blow it away and start a new install. (note: this would at least allow you
to start the OS to make any necessary backups prior to wiping the drive.)

To start the Recovery Console, start the computer from the Windows 2000
Setup CD or the Windows 2000 Setup floppy disks. If you do not have Setup
floppy disks and your computer cannot start from the Windows 2000 Setup CD,
use another Windows 2000-based computer to create the Setup floppy disks.
Press ENTER at the "Setup Notification" screen. Press R to repair a Windows
2000 installation, and then press C to use the Recovery Console. The
Recovery Console then prompts you for the administrator password. If you do
not have the correct password, Recovery Console does not allow access to the
computer. If an incorrect password is entered three times, the Recovery
Console quits and restarts the computer. Note If the registry is corrupted
or missing or no valid installations are found, the Recovery Console starts
in the root of the startup volume without requiring a password. You cannot
access any folders, but you can carry out commands such as chkdsk, fixboot,
and fixmbr for limited disk repairs. Once the password has been validated,
you have full access to the Recovery Console, but limited access to the hard
disk. You can only access the following folders on your computer: drive
root, %systemroot% or %windir%

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
| I'm getting the same error. Doesn't matter if system cold boots or reboots
| when warm. Ran chkdsk /r and found and fixed some errors. Ran it again and
no
| errors found. Appears to be a corrupt registry issue. Any ideas?
|
| "Jon" wrote:
|
| > From a cold startup my Windows 2000 system starts to bootup. It gets to
the graphical windows 2000 start up screen (the white blocks get right to
the end) just before the GUI appears and it reboots. It does this 3 times
and then goes into Windows normally. A blue screen briefly appears with the
following information before it reboots:
| >
| > STOP: c0000218 (registry file failure)
| > The Registry cannot load the hive (file):
| > \systemRoot\System32\config\SOFTWARE
| > or it's log or alternate.
| > It is corrupt, absent or not writable
| > Beginning dump of physical memory
| > Physical memory dump complete.
| > Contact your system technical support group.
| >
| >
| > When I finally get into Windows The event log has recorded the
following:
| >
| > The computer has rebooted from a bugcheck. The bugcheck was: 0xc0000218
(0xe166e148, 0x00000000, 0x00000000, 0x00000000). Microsoft Windows 2000
[v15.2195]. A dump was saved in: C:\WINNT\Minidump\Mini010405-01.dmp.
| > Any ideas what this might be to do with?
| >
| > It always happens each day on a cold startup. It doesn't tend to happen
if I reboot it whilst it's been on for a while.
| >
| > Any ideas what might be causing this?
 
I've downloaded the chkreg.exe but have not made the 6 disks yet becuase the
links all take me to Windows XP setup disks. I've got Windows 2000 what
should I use?

Thanks

Jon.

Leonard Severt said:
I'm getting the same error. Doesn't matter if system cold boots or
reboots when warm. Ran chkdsk /r and found and fixed some errors. Ran
it again and no errors found. Appears to be a corrupt registry issue.
Any ideas?

Jon said:
From a cold startup my Windows 2000 system starts to bootup. It gets
to the graphical windows 2000 start up screen (the white blocks get
right to the end) just before the GUI appears and it reboots. It
does this 3 times and then goes into Windows normally. A blue screen
briefly appears with the following information before it reboots:

STOP: c0000218 (registry file failure)
The Registry cannot load the hive (file):
\systemRoot\System32\config\SOFTWARE
or it's log or alternate.
It is corrupt, absent or not writable
Beginning dump of physical memory
Physical memory dump complete.
Contact your system technical support group.


When I finally get into Windows The event log has recorded the
following:

The computer has rebooted from a bugcheck. The bugcheck was:
0xc0000218 (0xe166e148, 0x00000000, 0x00000000, 0x00000000).
Microsoft Windows 2000 [v15.2195]. A dump was saved in:
C:\WINNT\Minidump\Mini010405-01.dmp. Any ideas what this might be to
do with?

It always happens each day on a cold startup. It doesn't tend to
happen if I reboot it whilst it's been on for a while.

Any ideas what might be causing this?
Click to expand...
Click to expand...

When you have a corrupt registry there are 2 ways to fix it.

1. Use the chkreg utility.
http://www.microsoft.com/downloads/details.aspx?FamilyID=56d3c201-2c68-
4de8-9229-ca494362419c&displaylang=en

Follow the instructions with it to make the boot disk which will then
automatically run it.

2. Copy a backup of the registry hive in recovery console. In the
Windows\repair folder you will find the original registry hives that
were created at the time Windows was installed. In addition if you have
ever made an ERD or a system state backup with NTBackup there will be a
regback folder under repair that will contain the more recent copies of
the registry that were saved at that time.

Boot to recovery console
Check the windows\repair folder to see if you have a regback folder
Change to the windows\system32\config folder (this is where the live
registry is stored)
Rename which every registry hive has the problem (software, system, etc)
Copy the registry hive from either windows\repair or windows\repair
\regback.

One of these methods will work. I would try chkreg first.

Leonard Severt
Microsoft Enterprise Support
Click to expand...
 
I've downloaded the chkreg.exe but have not made the 6 disks yet becuase the
links all take me to Windows XP setup disks. I've got Windows 2000 SP4 what
should I use?

Thanks

Jon.
Leonard Severt said:
I'm getting the same error. Doesn't matter if system cold boots or
reboots when warm. Ran chkdsk /r and found and fixed some errors. Ran
it again and no errors found. Appears to be a corrupt registry issue.
Any ideas?

Jon said:
From a cold startup my Windows 2000 system starts to bootup. It gets
to the graphical windows 2000 start up screen (the white blocks get
right to the end) just before the GUI appears and it reboots. It
does this 3 times and then goes into Windows normally. A blue screen
briefly appears with the following information before it reboots:

STOP: c0000218 (registry file failure)
The Registry cannot load the hive (file):
\systemRoot\System32\config\SOFTWARE
or it's log or alternate.
It is corrupt, absent or not writable
Beginning dump of physical memory
Physical memory dump complete.
Contact your system technical support group.


When I finally get into Windows The event log has recorded the
following:

The computer has rebooted from a bugcheck. The bugcheck was:
0xc0000218 (0xe166e148, 0x00000000, 0x00000000, 0x00000000).
Microsoft Windows 2000 [v15.2195]. A dump was saved in:
C:\WINNT\Minidump\Mini010405-01.dmp. Any ideas what this might be to
do with?

It always happens each day on a cold startup. It doesn't tend to
happen if I reboot it whilst it's been on for a while.

Any ideas what might be causing this?
Click to expand...
Click to expand...

When you have a corrupt registry there are 2 ways to fix it.

1. Use the chkreg utility.
http://www.microsoft.com/downloads/details.aspx?FamilyID=56d3c201-2c68-
4de8-9229-ca494362419c&displaylang=en

Follow the instructions with it to make the boot disk which will then
automatically run it.

2. Copy a backup of the registry hive in recovery console. In the
Windows\repair folder you will find the original registry hives that
were created at the time Windows was installed. In addition if you have
ever made an ERD or a system state backup with NTBackup there will be a
regback folder under repair that will contain the more recent copies of
the registry that were saved at that time.

Boot to recovery console
Check the windows\repair folder to see if you have a regback folder
Change to the windows\system32\config folder (this is where the live
registry is stored)
Rename which every registry hive has the problem (software, system, etc)
Copy the registry hive from either windows\repair or windows\repair
\regback.

One of these methods will work. I would try chkreg first.

Leonard Severt
Microsoft Enterprise Support
Click to expand...
 
Jon said:
http://www.microsoft.com/downloads/details.aspx?FamilyID=56d3c201- 2c68-
Click to expand...

Jon,

If you look at the instructions for this they say

Instructions
Before you download this tool, you will need to download the Windows XP
Professional Setup Boot Disks: Windows XP Professional Utility: Setup
Disks for Floppy Boot Install
This will require six floppy disks. Be sure to label the disks in order
in which you use them for the download. You will need the disk numbers
later.


As you see they tell you to use the Windows XP Disk.

Good luck

Leonard Severt
Microsoft Enterprise Support
 
OK download the utils created my xp boot disks modifyed the 6 disk,
restarted with disk 1 in gradually put each disk in as it asks for it. It
then gives me the option of installing xp, system recovery (repair) or to
quit

Which option should I be selecting, repair I assume?

Thanks,

Jon
 
I just had this problem on a Windows 2000 server this morning. How did
you get into DOS? I'm running a Dell
and it allows me into a setup utility and a RAID
config utility, but upon escape it just attempts another
re-boot. I cannot break out to DOS, I just see a C:
prompt fly by before it starts the RAID utility.


*From a cold startup my Windows 2000 system starts to bootup. It
gets to the graphical windows 2000 start up screen (the white blocks
get right to the end) just before the GUI appears and it reboots. It
does this 3 times and then goes into Windows normally. A blue screen
briefly appears with the following information before it reboots:

STOP: c0000218 (registry file failure)
The Registry cannot load the hive (file):
\systemRoot\System32\config\SOFTWARE
or it's log or alternate.
It is corrupt, absent or not writable
Beginning dump of physical memory
Physical memory dump complete.
Contact your system technical support group.


When I finally get into Windows The event log has recorded the
following:

The computer has rebooted from a bugcheck. The bugcheck was:
0xc0000218 (0xe166e148, 0x00000000, 0x00000000, 0x00000000).
Microsoft Windows 2000 [v15.2195]. A dump was saved in:
C:\WINNT\Minidump\Mini010405-01.dmp.
Any ideas what this might be to do with?

It always happens each day on a cold startup. It doesn't tend to
happen if I reboot it whilst it's been on for a while.

Any ideas what might be causing this? *
Click to expand...
 
If the system hive is corrupt, and assuming you already tried LKG (F8 and
choose Last Known Good), It may be possible to rename the system hive found
in
%windir%\system32\config\system
to system.old
then rename
%windir%\system32\config\system.alt
to
%windir%\system32\config\system

You can also try using the most recent backup found in
%windir%\repair\regback

If that fails you haven't much choice but to copy/ use the
original-as-installed system hive from
%windir%\repair\system
to
%windir%\system32\config\system
You'll need to reinstall the device drivers for any hardware added since the
original OS install.

To start the Recovery Console, start the computer from the Windows 2000
Setup CD or the Windows 2000 Setup floppy disks. If you do not have Setup
floppy disks and your computer cannot start from the Windows 2000 Setup CD,
use another Windows 2000-based computer to create the Setup floppy disks.
Press ENTER at the "Setup Notification" screen. Press R to repair a Windows
2000 installation, and then press C to use the Recovery Console. The
Recovery Console then prompts you for the administrator password. If you do
not have the correct password, Recovery Console does not allow access to the
computer. If an incorrect password is entered three times, the Recovery
Console quits and restarts the computer. Note If the registry is corrupted
or missing or no valid installations are found, the Recovery Console starts
in the root of the startup volume without requiring a password. You cannot
access any folders, but you can carry out commands such as chkdsk, fixboot,
and fixmbr for limited disk repairs. Once the password has been validated,
you have full access to the Recovery Console, but limited access to the hard
disk. You can only access the following folders on your computer: drive
root, %systemroot% or %windir%

To start the recovery console you'll want to boot the Windows 2000 setup
disks or CD-Rom. The set of four install disks can be created from your
Windows 2000 CD-Rom; change to the \bootdisk directory on the CD-Rom and
execute makeboot.exe (from dos) or makebt32.exe (from 32 bit) and follow the
prompts.

Then *F6* very early and very important (at setup is inspecting your system)
in the setup to prevent drive controller detection, and select S to specify
additional drivers. Then later you'll be prompted to insert the manufacturer
supplied Windows 2000 driver for your raid controller in drive "A"


--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
|
| I just had this problem on a Windows 2000 server this morning. How did
| you get into DOS? I'm running a Dell
| and it allows me into a setup utility and a RAID
| config utility, but upon escape it just attempts another
| re-boot. I cannot break out to DOS, I just see a C:
| prompt fly by before it starts the RAID utility.
|
|
|
| Jon wrote:
| > *From a cold startup my Windows 2000 system starts to bootup. It
| > gets to the graphical windows 2000 start up screen (the white blocks
| > get right to the end) just before the GUI appears and it reboots. It
| > does this 3 times and then goes into Windows normally. A blue screen
| > briefly appears with the following information before it reboots:
| >
| > STOP: c0000218 (registry file failure)
| > The Registry cannot load the hive (file):
| > \systemRoot\System32\config\SOFTWARE
| > or it's log or alternate.
| > It is corrupt, absent or not writable
| > Beginning dump of physical memory
| > Physical memory dump complete.
| > Contact your system technical support group.
| >
| >
| > When I finally get into Windows The event log has recorded the
| > following:
| >
| > The computer has rebooted from a bugcheck. The bugcheck was:
| > 0xc0000218 (0xe166e148, 0x00000000, 0x00000000, 0x00000000).
| > Microsoft Windows 2000 [v15.2195]. A dump was saved in:
| > C:\WINNT\Minidump\Mini010405-01.dmp.
| > Any ideas what this might be to do with?
| >
| > It always happens each day on a cold startup. It doesn't tend to
| > happen if I reboot it whilst it's been on for a while.
| >
| > Any ideas what might be causing this? *
|
|
|
| --
| uldmjl
| ------------------------------------------------------------------------
|
| ------------------------------------------------------------------------
| View this thread: http://www.mcse.ms/message1326358.html
|
 
Back
Top