loafman@convexe.UUCP (02/16/88)
I too have the DTK BIOS and have had no troubles with it. What makes you think it is not compatible with the std AT BIOS?? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Kenneth W. Loafman @ CONVEX Computer Corp, Dallas, Texas | All opinions Voice: work: (214) 952-0829 home: (214) 964-1250 | are my own, USPSnail: 1705 Coit Rd #2101, Plano, Tx 75075 | of course. UUCP: ihnp4!convex!loafman | CompuServe: 72345,233 | ...KWL ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
cbunjiov@sun-oil.ads.com (Charleen Bunjiovianna) (02/18/88)
In article <63200029@convexe> loafman@convexe.UUCP writes: > >I too have the DTK BIOS and have had no troubles with it. What makes >you think it is not compatible with the std AT BIOS?? > Have you tried running Kermit 2.3? I have, both at home and at work. It runs fine on the Compaq portables we have in the office. On my AT clone, I get a "Program too large to fit in memory". Hard to believe, since I have 1 meg RAM and Kermit is only ~181K. Oh yes, I'm running DOS 3.2. I'm open to other explanations... Charleen
murillo@sigi.Colorado.EDU (Rodrigo Murillo) (02/18/88)
In article <2458@zodiac.UUCP> cbunjiov@ads.com (Charleen Bunjiovianna) writes: >In article <63200029@convexe> loafman@convexe.UUCP writes: >> >>I too have the DTK BIOS and have had no troubles with it. What makes >>you think it is not compatible with the std AT BIOS?? >> >Have you tried running Kermit 2.3? I have, both at home and >at work. It runs fine on the Compaq portables we have in the office. >On my AT clone, I get a "Program too large to fit in memory". >Hard to believe, since I have 1 meg RAM and Kermit is only ~181K. >Oh yes, I'm running DOS 3.2. > >I'm open to other explanations... I'd be surprised if this was due to BIOS incompatabilties. Do you run any memory resident programs? These things eat up memory of course. You have a meg of RAM, but DOS can only use 640k of this to load programs. I'd suggest you run a chkdsk on your clone just before loading Kermit. This will report to you how much memory you actually have free, which is quite different (usually) that what your system is configured for. See how it compares with the Kermit requirements. The best way to check to see where your problem lies is to rename your autoexec.bat and config.sys files (to *.sav or something), reboot your machine, and run kermit on an empty system. This way the only interaction is just DOS and Kermit. Let me know if this works. What clone is this anyway? -- ----------- Rodrigo Murillo, UC - Boulder (303)761-0410 ----------- murillo@boulder.Colorado.EDU -or- ..{hao|nbires}!boulder!murillo (Machines have less problems. I'd like to be a machine. -- Andy Worhol)