ThinkPad networking died

Win98SE. TP770E.

It was working. Now it isn't after I didn't use it for a long time.

I'm seeing signs that the driver installation isn't finding all the
right files on either the machine or the installation CD - altho it did
work before. What is msodisup.vxd?

BTW, could someone remind me why the system often calls for files that
can't be found on the install CD?

Jim L via the eCS 1.15 version of OS/2

--
Help stamp out stupidity; send terrorists to the ACLU.

(E-Mail Removed) wrote:

>Win98SE. TP770E.
>
>It was working. Now it isn't after I didn't use it for a long time.
>
>I'm seeing signs that the driver installation isn't finding all the
>right files on either the machine or the installation CD - altho it did
>work before. What is msodisup.vxd?
>
>BTW, could someone remind me why the system often calls for files that
>can't be found on the install CD?
>
>Jim L via the eCS 1.15 version of OS/2

MSODISUP.VXD is a Windows 98 component file that is found in the
Net9.cab file on Windows 98 Cd for both the original release and
second edition, It is described as "Windows ODI to NDIS Mapper".

Often a hardware device requires a file or files that are provided by
the hardware manufacturer and which are not included on the Windows
CDs. This is especially true if the hardware item is a specialty
product with a relatively small market or if it a product that was
introduced after the Windows version was released.

Try removing the entry for the device from Device Manager and
rebooting the computer to allow it to redetect the device. But before
doing so make sure you go to the IBM web site and get the latest
Windows 98 drivers for your specific Thinkpad model.

Good luck

Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2006)
On-Line Help Computer Service
http://onlinehelp.bc.ca

Ron Martell <(E-Mail Removed)> said:

>(E-Mail Removed) wrote:

>>Win98SE. TP770E.
>>
>>It was working. Now it isn't after I didn't use it for a long time.
>>
>>I'm seeing signs that the driver installation isn't finding all the
>>right files on either the machine or the installation CD - altho it did
>>work before. What is msodisup.vxd?
>>
>>BTW, could someone remind me why the system often calls for files that
>>can't be found on the install CD?
>>
>>Jim L via the eCS 1.15 version of OS/2

>MSODISUP.VXD is a Windows 98 component file that is found in the
>Net9.cab file on Windows 98 Cd for both the original release and second
>edition, It is described as "Windows ODI to NDIS Mapper".

>Often a hardware device requires a file or files that are provided by
>the hardware manufacturer and which are not included on the Windows
>CDs. This is especially true if the hardware item is a specialty
>product with a relatively small market or if it a product that was
>introduced after the Windows version was released.

I should reword my (rhetorical) question. Why does the system call for
the installation CD for files the programmers know very well are buried
in cab files? Then complain that the file isn't on the CD? It's just
plain sloppy.

>Try removing the entry for the device from Device Manager and rebooting

Hm, no new device. I think I turned on the wrong networking
something-or-other. Maybe Network Meeting.

>Good luck

>Ron Martell Duncan B.C. Canada

Thanks.

Jim L via the eCS 1.15 version of OS/2

--

(E-Mail Removed) wrote:


>I should reword my (rhetorical) question. Why does the system call for
>the installation CD for files the programmers know very well are buried
>in cab files? Then complain that the file isn't on the CD? It's just
>plain sloppy.
>

If they are operating system files (e.g. part of Windows) then it may
not be possible for the programmers to get licensing permission from
Microsoft to include copies of these files with their application.

Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2006)
On-Line Help Computer Service
http://onlinehelp.bc.ca

Ron Martell <(E-Mail Removed)> said:

>If they are operating system files (e.g. part of Windows) then it may
>not be possible for the programmers to get licensing permission from
>Microsoft

I'm talking about the OS programmers. It's the system (that is, the OS
programmers) that's calling for files that are buried in cab files in
this case.

Altho Microsoft isn't exactly known for its friendly attitude toward
outside programmers. Witness: the EU fines against them.

Jim L via the eCS 1.15 version of OS/2

--

(E-Mail Removed) wrote:

>Ron Martell <(E-Mail Removed)> said:
>
>>If they are operating system files (e.g. part of Windows) then it may
>>not be possible for the programmers to get licensing permission from
>>Microsoft
>
>I'm talking about the OS programmers. It's the system (that is, the OS
>programmers) that's calling for files that are buried in cab files in
>this case.
>

Because not all of the files are needed for any given install. There
are many files that included that are optional and are only installed
when needed.

Or would you rather have Windows install the drivers for *every*
printer, *every* video card, and so forth; thereby cluttering up your
hard drive with hundreds, perhaps thousands, of totally extraneous
files?

As for compressing them into .cab files instead of storing them
uncompressed on the installation CD, that was a storage space and file
management decision that Microsoft made. The additional processing
time required to extract the files from the .CAB rather than just
copying the uncompressed file from the installation CD is miniscule.

What exactly do you think that Microsoft should have done with these
files?

Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2006)
On-Line Help Computer Service
http://onlinehelp.bc.ca

Ron Martell <(E-Mail Removed)> said:

>What exactly do you think that Microsoft should have done with these
>files?

Nothing. It should have made the system able to get them out of cabs.

Jim L via the eCS 1.15 version of OS/2

--

(E-Mail Removed) wrote:

>Ron Martell <(E-Mail Removed)> said:
>
>>What exactly do you think that Microsoft should have done with these
>>files?
>
>Nothing. It should have made the system able to get them out of cabs.
>

It can and does. If you copy the .cab files to the
\Windows\Options\Cabs folder (many OEM installs put them there) and
change the registry entry for their location from D:\Win98 to
C:\Windows\Options\Cabs the whole process is seamless.

Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2006)
On-Line Help Computer Service
http://onlinehelp.bc.ca