Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!midway!gargoyle!infopls!system From: system@infopls.UUCP (SYSOP) Newsgroups: comp.binaries.ibm.pc.d Subject: Re:Infoplus 135 Message-ID: Date: 9 Dec 90 21:10:55 GMT References: <1990Dec7.121658.25371@aplcen.apl.jhu.edu> Organization: INFOPLUS support, Wheeling, IL Lines: 29 Unknown writes: > In article <1990Dec6.112656.10927@pbs.org>, rfutscher@pbs.org says: > > As a matter of fact... The program tried to access my B: drive and > immediately hung (there wasn't a disk in the system). When I put a > disk in, it ignored it. I couldn't even three-finger-salute. I had to > turn off the computer. > > Carl Schelin > tcs@mailer.jhuapl.edu I was finally able to duplicate and track down the above bug. Turns out that it was code I used to determine if large partitions were available if DOS 3.3-3.99 was detected. I need to get the address of the driver for the particular drive, and then check a bit in it. Problem is, DOS's INT 25h uses 0=A, 1=B, etc.. The call to get the driver address uses 0=default, 1=A, etc.. One of those DUUHH type of errors. There's another DUHH error fixed in Infoplus 1.41, which should be out by the time you read this. (To check if I've really fixed the problem, try to go to a D: partition [if you don't have a D:, try doing something like SUBST D: C:\TEST, and make D: your default.] If it works, then that is the problem.) It seems as if some computers will time themselves out (may the so-called 'hangups' might time out after a couple minutes?) Others may just sit there forever, especially if B: is a 360K or 720K. --------------- Andrew Rossmann andyross@infopls.UUCP or ..!uunet!ddsw1!infopls!system Infoplus Support BBS +1 708 537 0247, 1200/2400, 24 hours