Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Novel disk error message

43 views
Skip to first unread message

Carole Brown

unread,
Jan 29, 2001, 3:03:31 PM1/29/01
to
Patty: I am sure you are on to something here. My IBM Aptiva 2137E26 came
from the factory with Win 95 and a bunch of Lotus Smart suit installed. I
never used it in Win 3.1 or in a workgroup. IBM may have upgraded from 3.1.
The Aptiva site has references to a disk being sent out to some machine
users, and then another replacement disk being sent. My particular 2137E26
was not on the list that received these disks. I never got any disks.
I was told by a friend to go into sysedit and remove the lines:
C:\Windows\lsl.com -after doing so nothing changed.
C:\Windows\odihlp.exe - I did and got another error:

A device file that is specified in the System.ini is damaged. It may be
needed to run windows.
You may need to run the Windows Setup Program again.
If the file is included in another software package, you may need to
reinstall the software that uses the file.
C:\Windows\system\msodisup.vdx
Press any key to continue.....
and Win 98 then opened again

So......I ran Windows Setup Program again and
Near the end it said "Insert disk labeled Novell Netware Dos Driver disk.
It is now required-provided by computer manufacturer." They never sent such
a disk and it is not in Win 95 or Win 98 either, apparently so I clicked on
"skip disk".
So I am back to square one and the original error message. I don't remember
seeing this Novell disk request the first time I installed Win 98 SE.

Now I am told I should remove "C:\Windows\system\msodisup.vdx", but am not
sure how to do so without getting into trouble . Also my existing odi
device driver seems to have a problem, it has a red x on it.
What do you think?
PS I did download the virus program you and several others mentioned. Thanks
....C

"PattyL" <plab...@XXmailandnews.com> wrote in message
news:ewRclSOhAHA.2024@tkmsftngp03...
> Once upon a time, Windows 3.1 or Windows for Workgroups was installed on
> this machine and was connecting to a Novell Netware server.
>
> Rename the Config.sys and Autoexec.bat files and then restart and see if
you
> get any errors. If you do, please let us know what they are. It is
possible
> that Windows was installed on your system from a directory on a Netware
> server and that whoever manufactured the PC forgot to remove the files
that
> allowed them to connect to their server.
>
> If you are counting on the Ms Antivirus to protect you from Virus, I'd
> sugest that you don't. I do not believe that you can update the virus
> signature list for it anymore which means that no virus written after 1995
> would be detected. This is not good.
>
> You can download good antivirus software at no cost and updat the virus
> signature list on a regular basis. Here's one:
>
> http://antivirus.cai.com/
>
> PattyL
>
>
> Carole Brown <cbr...@kalama.com> wrote in message
> news:u755aDOhAHA.1396@tkmsftngp05...
> I recently upgraded from Windows 95 to Windows 98 SE on my home PC and now
> when I start windows I get a Win 98 screen, then a black screen with an
> error message. it says:
> " C:\>C:\windows\lsl.com
> bad command or file name.
> LSL
> Microsoft Workgroups
> ODI/NDIS3
> Mapper Version2.0
> initialiazation failed"
>
> Then when I hit Enter it does load the Windows98 start page and I can go
on
> from there. This isn't right but I have not been able to find a way to
> correct it and can find no references to LSL or what it would be .


PattyL

unread,
Jan 29, 2001, 7:33:47 PM1/29/01
to
Hi Carole,

Try this:

Rename Autoexec.bat file to Autoexec.old and then restart. This will get
rid of all of the Netware entries.

Go to Control Panel, Network and remove anything that says Netware or Novell
on it. Probably Novell Netware shell. Also, remove IPX/SPX protocol. You
don't need it to access the internet so if you are not on a network, you
don't need it.

If you see any Network adapter besides the Dial-up adapter, then remove that
as well. Probably Existing ODI driver.

Now okay your way out of this and restart when prompted. If you get any
errors on reboot, please let us know.

Another way that just might be a little simpler would be to remove Dial up
networking from Control Panel, Add/remove programs, Windows setup and then
remove every single thing that is left in Network properties. After
rebooting, add Dial-up Networking from Control Panel, Add/remove programs,
Windows setup. After doing this, be sure to go back to Network properties
and add TCP/IP and remove Netbeui and IPX/SPX.

Let us know what happens. Good luck!

PattyL

Reboot the system and see if you still


Carole Brown <cbr...@kalama.com> wrote in message

news:uZvTF6iiAHA.1940@tkmsftngp04...

Carole Brown

unread,
Jan 29, 2001, 10:10:59 PM1/29/01
to
Bless you! You are a genius!
I followed your first set of instructions:
There was already a file called autoexec.bat.old on C
It also had the C:\windows\lsl.com and the C:\windows\odihlp.exe files so I
put Rem in front of those again.
I didn't want to mess up dialing in to my ISP, but I did anyway because I
removed from the list in Network, "Client for Microsoft Networks" but I
called my Isp and he got it back so It could save my password. Otherwise it
worked out fine and I did need to remove the existing ODI driver. No error
message anymore. Thanks so much! Carole

"PattyL" <plab...@XXmailandnews.com> wrote in message
news:O#eM8RliAHA.2188@tkmsftngp02...

PattyL

unread,
Jan 30, 2001, 12:03:02 AM1/30/01
to
Thanks for the feedback! Glad to hear that the errors are gone!

PattyL


Carole Brown <cbr...@kalama.com> wrote in message

news:uKgB8omiAHA.1308@tkmsftngp02...

0 new messages