dd26+@andrew.cmu.edu (Douglas F. DeJulio) (08/06/87)
The main reason I am not using generic MS-DOS is that I have not yet written a device driver for the PC 6300's internal clock. Also, stuff like the mode command might like to know about the different graphics board in the things. Anyone out there made a public domain device driver for the clock, that somone could install in their config.sys? It'd be a step towards a little more freedom in chosing your DOS.
psfales@ihlpe.ATT.COM (Pete Fales) (08/07/87)
In article <MV66emy00W0Nt1A0NL@andrew.cmu.edu>, dd26+@andrew.cmu.edu (Douglas F. DeJulio) writes: > The main reason I am not using generic MS-DOS is that I have not yet > written a device driver for the PC 6300's internal clock. Also, > stuff like the mode command might like to know about the different > graphics board in the things. I have been using generic MS-DOS 3.2 on my 6300 for some time and have been quite pleased. Switching to 2K clusters gained about 3 megabytes on my 20MB disk. > Anyone out there made a public domain device driver for the clock, > that somone could install in their config.sys? It'd be a step > towards a little more freedom in chosing your DOS. At least two have been posted to the net. I wrote one and posted it, then someone else posted a different one a while later. -- Peter Fales UUCP: ...ihnp4!ihlpe!psfales work: (312) 979-7784 AT&T Information Systems, IW 1Z-243 1100 E. Warrenville Rd., IL 60566
ninja@bradley.UUCP (08/07/87)
RE: differences between MSDOS brands
If you are going to shop around for dos's, I'd highly recommend
you check out what the manuals look like, and what options on
utilities look like. A for instance :
Zenith's MSDOS 3.2 :
Backup utility has lots of nice, Zenith specific options
Manuals are bound in a cheap, paper binder (won't hold up
long if heavily used).
IBM's MSDOS 3.2 :
Backup utility has nice options, but different from Zenith's and
not as many.
Manuals are nicely bound.
Can't say much about AT&T's (got it but haven't played with it much),
but I think you get the gist of what I mean. Price wise, it'll
cost you between $80 - $100 for 3.2 (from what I've seen).
Frank McGee
Bradley Universityaptr@ur-tut.UUCP (The Wumpus) (08/09/87)
In article <MV66emy00W0Nt1A0NL@andrew.cmu.edu> dd26+@andrew.cmu.edu (Douglas F. DeJulio) writes: >The main reason I am not using generic MS-DOS is that I have not yet >written a device driver for the PC 6300's internal clock. Also, >stuff like the mode command might like to know about the different >graphics board in the things. > >Anyone out there made a public domain device driver for the clock, >that somone could install in their config.sys? It'd be a step >towards a little more freedom in chosing your DOS. I have a set of drivers that read the AT&T Clock and set the MS-DOS clock by it and vice-versa. There was also a posting of a similar thing recently. (I am not sure if it was the same because I didn't bother with it.) One other note, I found that IBM-PC DOS 3.2 gained time very quickly (probably could be worded better). PC-DOS 3.3 does not have the same problem. I still find that the clock runs a little fast, but I believe it is because I am using the NEC V30 processor instead of the 8086. The only problem, outside of printing graphics screens, I have found concerning the AT&T ultra High Res mode is that FANSI Console does not let the computer switch to that screen. -- The Wumpus UUCP: {seismo,allegra,decvax}!rochester!ur-tut!aptr BITNET: aptrccss@uorvm Disclaimer: "Who? When? Me? It was the Booze!" - M. Binkley
wtm@neoucom.UUCP (08/10/87)
One good reason to use [MS] DOS from AT&T is that it has internal support for the 63xx's interanl battery backed clock. If you insist on using generic MS-DOS, there have been several postings of "setclock" that read the hardware clock and reprogram the 8253 timer chip t.o.d. interrupts to PeeCee compatible rates. If you insist, I could email you a copy of setclock if you can't find it in your system's news archives. We tested setclock on a system using a DOS 3.2 intended for Eposn brand computers. Setclock allowed the Epson DOS to apparently function correctly on the 6300. Note that there are reports of supposed subtle bugs in generic MS-DOS 3.2 floating around. One would assume that AT&T has cleaned up the port to be sufficiently well behaved on their hardware. --Bill (wtm@neoucom.UUCP)
psfales@ihlpe.ATT.COM (Pete Fales) (08/10/87)
In article <2612@ur-tut.UUCP>, aptr@ur-tut.UUCP (The Wumpus) writes: > In article <MV66emy00W0Nt1A0NL@andrew.cmu.edu> dd26+@andrew.cmu.edu (Douglas F. DeJulio) writes: > > The only problem, outside of printing graphics screens, I have found > concerning the AT&T ultra High Res mode is that FANSI Console does not > let the computer switch to that screen. What version of FANSI Console are you using? I had the same problem with with my first version of FANSI. When I reported it, the developers sent me version 2.00 and everything works fine. It also handles the NUM and CAPS LOCK LEDs correctly. -- Peter Fales UUCP: ...ihnp4!ihlpe!psfales work: (312) 979-7784 AT&T Information Systems, IW 1Z-243 1100 E. Warrenville Rd., IL 60566
abell@polyslo.UUCP (08/10/87)
> The main reason I am not using generic MS-DOS is that I have not yet > written a device driver for the PC 6300's internal clock. Also, > stuff like the mode command might like to know about the different > graphics board in the things. > Anyone out there made a public domain device driver for the clock, > that somone could install in their config.sys? It'd be a step > towards a little more freedom in chosing your DOS. This was just recently posted, but here it is again. Make sure to run it thru uudecode first, then down load it, in binary mode to your P.C. Then enter a line in your config.sys file with DEVICE=CLOCKDEV.SYS. -------------------------- CUT HERE --------------------------------- begin 644 clockdev.sys M_____PB & C $-,3T-+)" @ $ +HP&% NB1X2 ,M64%%25QX&4R[% M'A( BD<"Q'\.#A\*P'4#Z8 / QW(#P#<B%T$#P$=$T\"'(7="@\"70D=P\S MP"[%'A( B4<2N .!ZP*T 2[%'A( B4<#6P<?7UI96%[+)HL%,]*[M07W\RZC M%@"+VB:*;0,FBDT"M/_-&OOKSK3^S1I2N+4%+O<F%@!: ]@FB1TFB&T#)HA- : B:(=04FB%4$ZZDNQ1X2 ,='#K\ C$\0ZYH% end Alan Bell Cal Poly State University San Luis Obispo, CA 93407 ...ihnp4!csun!polyslo!abell