|
PureBytes Links
Trading Reference Links
|
Forgot to add, take extreme care if you manually make changes to the
registry (back it up first), else if you make an incorrect change your
program/system may crash..
J. Rodney Grisham wrote:
>
> Jim Osborn wrote:
>
> > Before I go digging through all the various files I've saved over
> > the years, could someone enlighten me as to the various ways you
> > know of to point to a location for the security driver: ssiact.386.
> >
> > In my stock installation, there's a line in C:\windows\system.ini:
> >
> > [386Enh]
> > device=ssiact.386
> > ...
> >
> > and the driver itself lives in directory: C:\windows\system
>
> Same for my NT installation of TS 4.
>
> >
> > I'm trying to fire up TS under Wabi in Linux, and I get a message
> > when I fire up the server that "ssiact.386 is not loaded" so I'm
> > hoping with a bit more explicit pointer in the or_serve.ini, or
> > somewhere like that, I can get the driver recognised.
> >
> > I seem to recall this is an issue the NT folks have had to wrestle with.
> > Any pointers?
>
> The results from the command
> dir /s ssi*.*
> on a Win NT system are:
>
> Directory of C:\WINDOWS\system
> 09/07/96 07:51a 40,601 SSIACT.386
>
> Directory of C:\WINDOWS\SYSTEM32
> 10/15/94 06:00a 58,880 SSIREGI.EXE
> 10/15/94 06:00a 71,680 SSIREGM.EXE
> 09/07/96 07:51a 16,384 SSIVDDP.1
> 09/07/96 07:51a 16,384 SSIVDDP.DLL
>
> Directory of C:\WINDOWS\SYSTEM32\DRIVERS
> 09/07/96 07:51a 628 SSIDDDP.SYS
> 09/07/96 07:51a 52,224 SSIPDDP.SYS
>
> Directory of C:\WINDOWS\SYSTEM32\inetsrv
> 04/30/97 11:00p 47,888 SSINC.DLL
>
> There is no reference to any of these files in the (do nothing in NT)
> autoexec.bat or config.sys files.
>
> Rod
|