NetNews Usenet Archive 1992 #31/NN_1992_31.iso/spool/bit/listserv/win3l/11927

Text File | 1993-01-04 | 1.6 KB | 37 lines

Comments: Gated by [e-mail]
Path: sparky!uunet!wupost!gumby!yale!yale.edu!jvnc.net!darwin.sura.net!paladin.american.edu!auvm!MCIMAIL.COM!CALLAHAN
Message-ID: <72930104052227/[e-mail]>
Newsgroups: bit.listserv.win3-l
Date:         Mon, 4 Jan 1993 05:22:00 GMT
Sender:       Microsoft Windows Version 3 Forum <[e-mail]>
From:         CALLAHAN <[e-mail]>
Subject:      Stacker slows Windows startup?
Lines: 26

I installed Stacker 3.0 and everything was wonderful -- until I started
Windows 3.1. The startup sequence now takes about 1.5-2 minutes (used
to take about 20 seconds), with lots and lots of disk accessing. I per-
ceive no other performance problems, which leads me to believe it is a
problem allocating the temporary swap file. I tried setting it to NONE
for swap file, but I didn't notice much difference. I am loathe to try
a permanent swap file since I'd have to uninstall Stacker and reinstall
and it takes about 1.5 hours to compress my 140-meg disk.

This is the first computer I've seen act this way, and I've installed
Stacker on a half-dozen machines at work. Is my guess about the temp
swap file reasonable? If so, how can I change it? As a last resort,
I'm willing to try setting up a permanent swap file, but I'd have to
be very certain it was going to fix the problem since it's so much
work.

If it's not the swap file, what might it be? Note that my disk
controller will not allow 32-bit access, if that matters.

Thanks.

--michael--
[e-mail]

P.S. WIN3-L mail is erratic for me -- replying to the above email
address is more reliable.