brmorrow@uokmax.UUCP (Brett Morrow) (06/14/89)
I am looking for information on Dr Dos. I know this was asked for a while back by someone, but I saw no replies. If anyone out there has information on this product or uses it let me know, I have some question. I bought it and just installed it on my machine last night. I have not had much of a chance to use it. I can be contacted at the following addresses: ------------------------------------------------------------------------ Internet: brett@aardvark.ucs.uoknor.edu < best Bitnet : ausbam@uokmvsa UUCP : brmorrow@uokmax.UUCP -------------------------------------- Hope to hear for you.
dross@umn-d-ub.D.UMN.EDU (david ross) (06/16/89)
Several months back I posted an extensive list of bugs, some very malicious, in DR DOS. Some were confirmed, and passed on to the DR DOS development team, by a reader of this group who works for DR (thanks again!) Quite some time ago I wrote both DR and 2001 Sales (who distributes the thing), listing these and other bugs I'd found, and asked if new versions corrected the errors. I never received a response, and must therefore conclude that DR DOS is still broken. If you use TSR's, or have a "mixed media" system (i.e., 1 hard, 1 5", and one 3.5" disk drive), keep away from DR DOS; it could prove deadly.
frotz@drivax.UUCP (Frotz) (06/17/89)
Detailed questions about DR-DOS may be routed through me or directed to Compu$erve @ DRFORUM (area 4). <brmorrow@uokmax.UUCP (Brett Morrow) writes:> ] I am looking for information on Dr Dos. I know this was asked for a ] while back by someone, but I saw no replies. If anyone out there has ] information on this product or uses it let me know, I have some ] question. I bought it and just installed it on my machine last night. ] I have not had much of a chance to use it. Question: How did you come by a copy of DR-DOS? and what version is it? <The next day brmorrow@uokmax.UUCP (Brett Morrow) writes:> ] Yesterday I sent out mail about Dr Dos, I was looking for info. Well ] now I am looking for more info. I install Dr Dos and found some ] problems with it and I would like to hear from anyone with ] suggestions. ] a) i have DoubleDos and it does not seem to run under Dr Dos. When I ] moves to MsDos 3.3 I had to call and get an upgrade. I was going ] to call again, but I thought I would ask here first. I believe that the party line would be: "Buy Concurrent DOS if you want multitasking/multiple dos partitions." <DRI Tech Support writes:> We understand that Double DOS is looking for specific code segments within COMMAND.COM... Naturally we don't exactly have this sort of thing lying around... (unless... nah... they wouldn't give it to us anyway;-);-);-) You might see if the makers of Double DOS are interested in supporting DR DOS. If so, they can call DRI Tech Support. (1-408-646-6464) ] b) i got a copy pkzip ver .92 (i think), the self extracting one. i ] tried to run the program to get the zip package. it did not work. ] it ran and showed the filename and just ended. i booted msdos3.3 and ] tired it and it worked. i them rebooted under DR DOS and tried to run ] pkunzip on some zip files i had downloaded. it came back and started to ] run and then told me no files. i rebooted under msdos 3.3 and tried the ] same thing and it worked. PKWARE has a patch for this and DRI is working on our own patch. If you unzip on a floppy, this is reported to work fine. <dross@umn-d-ub.d.umn.edu (david ross) writes:> ] Several months back i posted an extensive list of bugs, some very ] malicious, in DR DOS. Some were confirmed, and passed on to the DR ] DOS development team, by a reader of this group who works for DR ] (thanks again!) <Frotz writes:> You're welcome. (Though I don't personally remember this, it could have been any of a number of other engineers who occaisionally read this group.) Marketing won't let me disseminate the number of bugs fixed recently, but there have been major improvements in supporting "nasty" DOS programs... ] Quite some time ago I wrote both DR and 2001 Sales (who distributes ] the thing), listing these and other bugs I'd found, and asked if new ] versions corrected the errors. I never received a response, and must ] therefore conclude that DR DOS is still broken. My apologies for the lack of response from Digital Research. What version of DR-DOS did you try and/or what was the approximate date of use. At this point, only engineers with *lots* of spare time can do anything more than browse USENET. (My excuse is that it is Friday afternoon;-) ] If you use TSR's, or have a "mixed media" system (i.e., 1 hard, 1 5.25", ] and one 3.5" disk drive), keep away from DR DOS; it could prove ] deadly. Any idea which TSRs? I have used a recent version (new beta in the last couple of weeks) with HISTORY, MARK/RELEASE, and some other TSRs with no problems that I could attribute to DR-DOS (more likely my debugging efforts;-). <DRI Tech Support writes:> What version were you running (3.35? The current release is 3.40)? What was your hardware environment? What do you mean by "deadly"? We are very interested in following up on this. [Frotz-Follow-up is much better on Compu$erve than on USENET as I actually have an real job;-] <Frotz writes:> Appologies to the net for the verbosity. Again requests for information can UNRELIABLY be sent through me or RELIABLY sent through Compu$erve @ DRFORUM (area 4). --Frotz @Digital Research, Incorporated amdahl!drivax!frotz 70 Garden Court, B15 (408) 649-3896 Monterey, California 93940 Ask for John Fa'atuai