Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!bloom-beacon!mit-eddie!uw-beaver!cornell!rochester!pt.cs.cmu.edu!b.gp.cs.cmu.edu!Ralf.Brown@B.GP.CS.CMU.EDU From: Ralf.Brown@B.GP.CS.CMU.EDU Newsgroups: comp.sys.ibm.pc Subject: Re: DESQview - who makes it? (now DV 2.24 bugs) Message-ID: <2402d183@ralf> Date: 22 Feb 89 15:28:03 GMT Sender: ralf@b.gp.cs.cmu.edu Lines: 138 In-Reply-To: <36336@tut.cis.ohio-state.edu> In article <36336@tut.cis.ohio-state.edu>, schanck@calorie.cis.ohio-state.edu (Christopher Schanck) writes: }In article <24009478@ralf> I write: }>And by all reports on the DESQVIEW conference on Fidonet, v2.24 is rotten to }>the core } }Could you summarize what the problems are with v2.24? Here are the relevant messages from the conference, shortened somewhat: From: Mike Davis @ 930/1 To: Blaine Korcel Msg #47, 12-Feb-89 10:04am Subject: Re: Dv 2.24 Bugs BK> I just encountered a crazy bug in 2.24. We just bought DV 386 which w BK> bundled with 2.24 of all things. I noticed that running an applicatio BK> quickbasic compiled to be specific but not exclusive, under DV would BK> prevent my application from seeing files ANYWHERE! I have since gone BK> back to our copy of 2.22 and all is working fine, 2.22 bugs excepted. BK> BK> A warning to ALL, DesqView 2.24 has some serious problems in accessing BK> files. GREAT! I saw that SAME bug two weeks ago and posted it here and on Quarterdeck's BBS as well as call Tech Support. At that time, they said no one else had reported the problem so they couldn't give "highest" priority to it. Sorry you have a problem, but glad for the company! From: Mark Moran To: Mike Davis @ 930/1 Msg #49, 14-Feb-89 10:47am Subject: Re: Dv 2.24 Bugs BK> A warning to ALL, DesqView 2.24 has some serious problems in accessing BK> files. MD> GREAT! I saw that SAME bug two weeks ago and posted it here and on MD> Quarterdeck's BBS as well as call Tech Support. I'm reluctantly joining this party. Installed 2.24 last PM, reinstalled 2.22 backup today. Last PM DV erased a whole directory for me (unrecoverable by Norton's). This means it moved the directory contents to God knows where. I jumped into a DOS window which happened to be in the directory where someone was up loading something from the BBS window and when he was finished everything was gone. Granted this isn't the smartiest thing to do, but I've played with DV 2.22 in a similar fashion without a problem. I hadn't fooled with 2.24 in this respect, but I guess this was some provactive testing. Too bad it wasn't with data I didn't care about. Another thing I've noticed with the few hours 2.24 was on my system: DSZ reports a serial port line area occasionally. This started immediately after installing 2.24. I wonder if it will now disappear that 2.22 is back on-line. From: Kurt Riegel To: Blaine Korcel Msg #51, 13-Feb-89 11:18pm Subject: RE:dv 2.24 Bugs I received DESQview's 2.24 version and find that it is rotten to the core. Got a FAX from Dan Sallitt at Quarterdect today confirming that it forgot how to find files, a zillion enraged users reported it, the fix has been found, and my disk is "in the mail". Sure. Actually, I've been using DV2.23a for some weeks and find it to be smooth as silk. All the dual communications instabilities of 2.22 and prior versions seem to be gone, and I have yet to witness a burp of any kind. As long as they don't "improve" it again like 2.24, I think we can expect a winner. From: Blaine Korcel To: Richard Huddleston Msg #69, 14-Feb-89 08:58pm Subject: RE: Dv 2.23 > I wonder what the fix from 2.23 and 2.24 are supposed to correct. From personal experience and frustration, I can assure you that 2.24 is a step backwards in technology. There are so many bugs that it is nearly useless for all but the simple user. Version 2.23 is by far the most stable with 2.22 falling in close behind. From: Bob Moravsik To: Mike Davis @ 930/1 Msg #70, 13-Feb-89 06:56pm Subject: RE: Dv 2.24 Mike...DV 2.24 causes bugs in RBBS...I had to drop back to 2.21...I verified the problem is in dv 2.24 and I think it is the way the files are accessed....Bob Moravsik From: Mike Davis @ 930/1 To: Clint Anglin Msg #76, 15-Feb-89 06:22am Subject: RE: Dv 2.24 CA> Can anyone tell me: how do you get Quarterdeck to send you the upgrade CA> I've been using DV 2.22 for quite awhile now and never received the 2. CA> upgrade, let alone 2.24. Do I have to send MORE money for these CA> maintenance upgrades? CA> -clint- You need to call Tech Support on the phone and hang on hold for 45 minutes or so, then they will send you an upgrade. The current upgrade (2.24) is supposed to fix the problems with handling COMM paramemters that so many people have complained about. Its supposed to be a major revision. However on my system, it is almost non-functional and my BBS can't find any of its support files, so 2.24 is completely useless for me. From: Paul Marwick To: Mark Moran Msg #69, 19-Feb-89 12:44am Subject: Re: Dv 2.24 Bugs -> I'm reluctantly joining this party. Installed 2.24 last PM, -> reinstalled 2.22 backup today. Last PM DV erased a whole directory -> for me (unrecoverable by Norton's). This means it moved the -> directory contents to God knows where. I've just encountered another peculiarity in 2.24. I use FU WAIT in several places. Doesn't work at all under 2.24 - if you're using a timed wait, the window just stops, has to be closed and reopened to get anything out of it. If using just WAIT, it doesn't count till the change of the minute, just drops straight to DOS. Also discovered that Lynx will not even load it. I'm _so_ glad I ARCed my 2.22 directory before installing it! Regards, Paul. -- UUCP: {ucbvax,harvard}!cs.cmu.edu!ralf -=-=-=- Voice: (412) 268-3053 (school) ARPA: ralf@cs.cmu.edu BIT: ralf%cs.cmu.edu@CMUCCVMA FIDO: Ralf Brown 1:129/31 Disclaimer? I claimed something? You cannot achieve the impossible without attempting the absurd.