I am having the same problem . I would like to extract the WINOA386.MOD
file from my *.cab files but cannot find which cab . My current
WINOA386.MOD file is corrupt . TIA for your help
> Glad to hear you found it....thanks for the feedback.
> > I found the DOS program causing the hang up. Thanks for your help.
[quoted text clipped - 21 lines]
> > > > > just sits there with the empty desktop until I power the PC down. Any
> > > > > suggestions?
Extract the file from the .cab files on your Windows CD, or from the .cab file
location on your hard drive, to the Windows\System folder, using the"Extract one
file" option of System File Checker (SFC). When using that method, you don't need
to know what .cab it's in....SFC searches for it.
Using SFC to extract a file:
http://www.rickrogers.org/sfc.htm#1pp
http://www.rickrogers.org/sfc.htm#2pp
HOW TO: Extract Original Compressed Windows Files:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;129605#5
Hmmm...WINOA386.MOD is named WINOA386.NEW in the .cab files, so SFC may not work.
WINOA386.NEW is in Win98_51.cab, on the 98SE disc.
It is in Win98_45.cab, on the Win98 original edition disc.
It is in Win98_38.cab on Disk 33 of the floppy disk set of Win98.
You can extract it from the .cab with a program like WinZip, ZipCentral, or PKZip

Signature
Glen Ventura, MS MVP Shell/User, A+
http://dts-l.org/goodpost.htm
> I am having the same problem . I would like to extract the WINOA386.MOD
> file from my *.cab files but cannot find which cab . My current
[quoted text clipped - 37 lines]
> down. Any
> > > > > > suggestions?
REE - 01 Apr 2006 02:48 GMT
Thank you glee ; the problem was that the WINOA386.MOD file was being
opened with Winamp "mod" files , and I didn't realize it . When I
unticked the mod file in Winamp file types , the WINOA386.MOD file
opened with windows application and everything was back to normal . The
WINOA386.MOD was named WINOA386.NEW and SFC did not work . It was in
Win98_51.cab . Thanks again for your help . I hope I was able to explain
> Extract the file from the .cabn, to the Windows\System folder, using
the"Extract one
> file" option of System File Checker (SFC). When using that method, you don't need
> to know what .cab it's in....SFC searches for it.
[quoted text clipped - 53 lines]
> > down. Any
> > > > > > > suggestions?
glee - 01 Apr 2006 04:41 GMT
WinAmp can play .MOD files which are "Music On Disc" files, but there is no reason
for it to open WINOA386.MOD on its own, unless you were trying to open that file
with WinAmp yourself. Unassociating the file type with WinAmp should not have had
any effect on the issue, AFAICS, unless you were double-clicking WINOA386.MOD, which
there would be no reason to do.
However, if your issue is resolved, more power to ya.

Signature
Glen Ventura, MS MVP Shell/User, A+
http://dts-l.org/goodpost.htm
> Thank you glee ; the problem was that the WINOA386.MOD file was being
> opened with Winamp "mod" files , and I didn't realize it . When I
[quoted text clipped - 74 lines]
> > > down. Any
> > > > > > > > suggestions?