From: The Drifter <drifter@c2.net>
To: cypherpunks@toad.com
Message Hash: a03c21e73d88bba19afedb68b5746a488276887ca6b9734be54b2762841a005a
Message ID: <Pine.SUN.3.94.960827181944.23478B-100000@infinity.c2.net>
Reply To: N/A
UTC Datetime: 1996-08-28 04:11:42 UTC
Raw Date: Wed, 28 Aug 1996 12:11:42 +0800
From: The Drifter <drifter@c2.net>
Date: Wed, 28 Aug 1996 12:11:42 +0800
To: cypherpunks@toad.com
Subject: Re: File System Encryption
Message-ID: <Pine.SUN.3.94.960827181944.23478B-100000@infinity.c2.net>
MIME-Version: 1.0
Content-Type: text/plain
On Wed, 28 Aug 1996 02:55:20 +0400, Wayne Clerke <wclerke@emirates.net.ae>
wrote:
>Tried secdev? Edgar Swank (author of secdrv) recently posted
>that secdev (note, not secdrv) does, in fact, uses 32 bit disk
>access with win95. Win95 reports that the secure device is in
>compatibility mode, but the host disk (and therefore the secure
>volume file) is being accessed in 32 bit (disk) mode. Not sure
>what issues there are with '32 bit FILE access' mode here.
>
>Sounds worth a try though. Please post the results if
>you try this.
>
I have actually had Secure File System, Secure Drive, and Secure Device
all installed with mounted volumes at the same time under Win95. However,
32bit file access is not the problem. When you load a TSR in Win95, the
operating system forces you into 16bit DOS compatability mode. I'm not a
kernal guru so I can't explain all the specifics, but it basically makes
95 act as Win-3.11 and looses multithreading (as it were) and creates
serious memory paging problems if you have >32mb installed.
Thanks for the reply though .. and if you need assitance with getting
SECDEV working under 95, just drop me a note.
Drifter
Return to August 1996
Return to “The Drifter <drifter@c2.net>”
1996-08-28 (Wed, 28 Aug 1996 12:11:42 +0800) - Re: File System Encryption - The Drifter <drifter@c2.net>