djo7613@hardy.u.washington.edu (Dick O'Connor) (01/15/91)
We use the screen-saver "explosiv" on several of our machines, usually run as a TSR out of autoexec.bat. I enjoy the displays, but we believe it may be responsible for some oddball breakdowns lately. Since explosiv (as I recall) was posted here Once Upon A Time, I'd like to find out if others have exper- ienced similar problems. 1) Our machines are linked to each other and share printers using LANtastic. After resuming a session that times into explosiv's display, we need to Retry the network connection the next time we want to print. Our Ethernet cards are all using IRQ=5; I don't know if explosiv is the culprit, but there is some circumstantial evidence relating to when the problems seem to happen. 2) If explosiv comes on during a PC Shell session (PC Tools DOS Shell), certain areas of the screen, once restored, have high-order bits changed so that they blink. Entering and exiting one of the menus restores order. 3) explosiv has locked up a few R:Base 5 sessions. I have little info on this problem at this point. I hope I'm wrong, because I like the program. Has anyone else had similar symptoms? A pointer to any previous discussion would be appreciated; our machine doesn't have any such articles in its archives right now. Thanks!! "Moby" Dick O'Connor djo7613@u.washington.edu Washington Department of Fisheries *I brake for salmonids* "Moby" Dick O'Connor djo7613@u.washington.edu Washington Department of Fisheries *I brake for salmonids*
ff76@vaxb.acs.unt.edu (Jhinuk Chowdhury) (01/16/91)
In article <14379@milton.u.washington.edu>, djo7613@hardy.u.washington.edu (Dick O'Connor) writes: > We use the screen-saver "explosiv" on several of our machines, usually run as > a TSR out of autoexec.bat. I enjoy the displays, but we believe it may be > responsible for some oddball breakdowns lately. Since explosiv (as I recall) > was posted here Once Upon A Time, I'd like to find out if others have exper- > ienced similar problems. > > (deletions . . . .) > > 2) If explosiv comes on during a PC Shell session (PC Tools DOS Shell), > certain areas of the screen, once restored, have high-order bits changed so > that they blink. Entering and exiting one of the menus restores order. > Yes, I and sevral of my colleagues have experienced this. It's very annoying, really! Additionally, if Explosiv is loaded as a TSR and I use the DOS print command on a rather large file that takes more time to print than the "wait-time-before- blanking-screen" specified to explosiv, then the printer activity ceases at the same time as the screen blanking is activated. Finally, although I am not completely sure of this - another TSR may be responsible, Explosiv may be confusing my DOS clock to change the date after midnight. Without any TSRs loaded, my DOS clock on the Compuadd 286 correctly changes over to the next date after midnight for *more than two successive nights* (I use MS-DOS 3.3). But with Explosiv, Vshield, Quickeys, and Clockon loaded as TSRs, the date does not roll-over at midnight. I suspect the culprit is Clockon, since I do not remember having this problem when I used ALARM in place of CLOCKON. > > I hope I'm wrong, because I like the program. Has anyone else had similar > symptoms? A pointer to any previous discussion would be appreciated; our > machine doesn't have any such articles in its archives right now. Thanks!! I wish a newer version that takes care of these problems is realed soon. > > "Moby" Dick O'Connor djo7613@u.washington.edu > Washington Department of Fisheries *I brake for salmonids* > "Moby" Dick O'Connor djo7613@u.washington.edu > Washington Department of Fisheries *I brake for salmonids* - Jhinuk.
drack@titan.tsd.arlut.utexas.edu (Dave Rackley) (01/17/91)
I've recently experienced strange problems on my machine. I thought it was just the machine's age, but I'm using explosiv (v 1.22), too. My system runs DOS v3.2, 4DOS v3.02a, *occasionally* my machine locks up and has to be rebooted. Usually the lock-ups occur after explosiv should have taken over. BTW just sharing experiences--not complaining about explosiv. -- DISCLAIMER? I don't know anything 'bout any ol' disclaimer! +=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=+ | David Rackley | | | Applied Research Laboratories | It's OK to be a martyr, as long as | | The University of Texas | you don't bring your own firewood. | | Austin, TX. 78758 | -- Dr. James Rigby | +=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=+
drack@titan.tsd.arlut.utexas.edu (Dave Rackley) (01/17/91)
In article <16660002@col.hp.com> mikek@col.hp.com (Mike Karin) writes: [stuff deleted] > I do this because, in addtion to the blinking lights, my HP Mouse stops > working when I resume PC SHELL after explosiv. I asked explosiv's author > about this and he couldn't offer any advise concerning an HP mouse. My logitech mouse also stops after explosiv takes over. -- DISCLAIMER? I don't know anything 'bout any ol' disclaimer! +=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=+ | David Rackley | | | Applied Research Laboratories | It's OK to be a martyr, as long as | | The University of Texas | you don't bring your own firewood. | | Austin, TX. 78758 | -- Dr. James Rigby | +=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=+
marty@wuphys.wustl.edu (Marty Olevitch) (01/17/91)
The documentation file that comes with explosiv says that it halts the running process until a key is pressed. The ss3 screen saver on the simtel-20 archives doesn't have this drawback, but it doesn't have the fancy display either. Marty Olevitch Internet: marty@wuphys.wustl.edu Washington University UUCP: uunet!wugate!wuphys!marty Physics Department, Campus Box 1105 Bitnet: marty@wuphys.WUSTL St Louis MO 63130 USA Tel: (314) 889-6285
keith@curry.uchicago.edu (Keith Waclena) (01/17/91)
In article <1991Jan16.121030.44263@vaxb.acs.unt.edu> ff76@vaxb.acs.unt.edu (Jhinuk Chowdhury) writes:
Finally, although I am not completely sure of this - another TSR
may be responsible, Explosiv may be confusing my DOS clock to
change the date after midnight. Without any TSRs loaded, my DOS
clock on the Compuadd 286 correctly changes over to the next date
after midnight for *more than two successive nights* (I use MS-DOS
3.3). But with Explosiv, Vshield, Quickeys, and Clockon loaded as
TSRs, the date does not roll-over at midnight.
Well, on my Compaq 286, also running with many TSRs (none of the ones
you mention, though), Explosiv seems to cause my clock to simply stop
dead during the time that Explosiv blanks the screen: if I leave the
machine for 3 hours, when I come back the clock is off by three hours.
It's very easy to test and see that the immediate cause is Explosiv
blanking the screen.
The exact same behavior occurs on another machine (not a Compaq, not
running any TSRs except for Explosiv).
*Very* annoying, as it's such a nice screen saver. But I've had to
stop using it.
Keith WACLENA keith@tira.uchicago.edu
CILS / TIRA / U of Chicago keith%tira@uchimvs1.bitnet
1100 E.57th.St Chi IL 60637 USA ...!uunet!tira.uchicago.edu!keith
History lives in the books at home
--
Keith WACLENA keith@tira.uchicago.edu
CILS / TIRA / U of Chicago keith%tira@uchimvs1.bitnet
1100 E.57th.St Chi IL 60637 USA ...!uunet!tira.uchicago.edu!keith
History lives in the books at homemikek@col.hp.com (Mike Karin) (01/19/91)
>We have our machines at work linked using HP Office share. I am using >explosiv and periodically, after resuming a session from explosive, all >of my network connections are broken and have to be restarted. The >Starlan 10 card is using IRQ=5. This sounds like it might be the same >problem. Since I had been puzzled over this problem and this was the first clue as to the culprit, I stopped using explosiv for a few days. Net connections that were breaking an average of 2 times a day have not broken at all since I stopped using explosiv. This is too bad because I really liked the program. I'm going to forward a copy of this notes string to-date to explosiv's author. Mike Karin Hewlett-Packard Co. Colorado Springs Division mikek@col.hp.com