CompuServe Thread

#more monitor debugging

8 messages in this thread
#133158From: Gayle Lee FairlessFeb 22, 1994 12:22 AM
Brian, Well, I found out the cause of the error. Somehow the memory manager with my OS was messing up the bootup, perhaps with incorrect parameters. Things work fine with the memory manager or with the Janus driver. Anyway, I have more exploring to do! Sincerely, (Mr.) Gayle Lee Fairless 'Perfessor Fearless' from the Rocket City! via AutoPilot 1.03a
#133255From: Ron LegroFeb 22, 1994 12:43 PM
awhile? How much comppatibility with title from other interactive machines? [D I have never been an IBM fan but they are venturing into cd rom technology in a big big way.
#133963From: Gayle Lee FairlessFeb 26, 1994 8:55 PM
Ron, I haven't tried anything on the IDE connection yet. (I need to refill my piggy bank.) I haven't even tested the extra parallel and serial ports yet. Fortunately, the small 13" multisync works fine. The memory manager that came with DRDOS 6.0 was clobbering the 386 bridgeboard (BB). Evidently, upper memory is sensitive to unauthorized or unknowing poking around! Running the BB with no memory manager or with the Janus EMM.SYS works. I wish I could get some more memory freed up in conventional memory. My SuperStor driver from Addstor takes up 50K. Norton Commander V3.0 takes up 12K. Anyway, I cannot run WordPerfect 6.0 for DOS in graphics mode due to lack of memory. At least it runs nicely in text mode. I cannot use an alternate configuration in which I don't use the Addstor compression software because WordPerfect is on the compressed D: drive. I left my boot drive C: uncompressed just in case I had trouble with the SuperStor stuff. Sincerely, (Mr.) Gayle Lee Fairless 'Perfessor Fearless' from the Rocket City! via AutoPilot 1.03a
#134190From: Ron LegroFeb 27, 1994 7:16 PM
Gayle: Lucky I didn't try the DRDOS 6 memory manager. I stuck with the one that came with the Bridgeboard, EMM.SYS. However, I *have* been running the DR DOS HIDOS.SYS and HIDOS drivers without trouble and together they seem to help performance AND they let you move stuff out of the lower 640K, including buffers (use HIBUFFERS) and other stuff that normally can't load anywhere but lower memory. Check it out. I've got 5 megs of ZIPs on my BB and when all is said and loaded the DR DOS Mem utility reports: Total Available Conventional 640K 615K Upper 16K 2.6K High 64K 8.0K Extended 4096K 0K Ext. via XMS N/A 4032K EMS 636K 262K This is with the 256K VGA video on the STB board. You can also use the HIDOS command to grab some video memory, but it probably bumps you down to EGA mode; haven't tried it with this board, but it worked with an earlier VGA card just fine, giving me a 704K base system. I wonder what'll happen when I up to Novell DOS 7.0? maybe the Bridgeboard won't work with its memory manager either. Wouldn't be the end of the world. I haven't tried Superstor on the IDE drive, as I'm suspicious of it. What are you running Superstor on if you aren't using the IDE controller? BTW, you should bite the bullet and upgrade to Autopilot 1.061. Much nicer in many respects (like a message thread feature to locate stuff fast) and the GIF on-line viewer. Seems to run a tad faster, too.
#134788From: Gayle Lee FairlessMar 4, 1994 1:11 AM
Ron, I don't have Novell 7 although I have been over to the NDSG forum. It may be shipping; however, I have not gotten any upgrade notice. I am using SuperStor on the D: drive of my hardcard which has two 20 Meg harddrives on it. (Marion Deland can tell you what to look for.) I left the C: drive uncompressed just in case SuperStor gave me a problem since C: is my boot drive. Before the hardcard, I had successfully used the SuperStor utility on the MAKEAB pseudo-harddrive. It works there, too! Of course, the hardcard supersedes the emulation of the MAKEAB drive. I have not connected anything to the IDE controller as of yet. The extra parallel port and serial port have not been tested yet, either. Now I do have the ports hooked up. I would love to see a copy of your CONFIG.SYS and AUTOEXEC.BAT files! Or, at least the part that pertains to HIDOS.SYS and EMM.SYS. Presently, I am just using the EMM.SYS driver. Are you saying that I can use it with the DRDOS HIDOS.SYS driver? I would use Autopilot 1.061 if it didn't crash my system whenever I attempted to use the message reader or the editor. I got tired of rebooting and losing whatever else was running. The crashes even wiped out RAD:! Here is my MEM /A output: Address DBD Owner DDBD Size DBD Type 0:0000 ——– A0000h, 655,360 ————- RAM 0:0000 ——– 400h, 1,024 Interrupt vectors 40:0000 ——– 100h, 256 ROM BIOS data area 50:0000 DR DOS 200h, 512 DOS data area 70:0000 DR BIOS B60h, 2,912 Device drivers 70:050B PRN Built-in device driver 70:051D LPT1 Built-in device driver 70:052F LPT2 Built-in device driver 70:0541 LPT3 Built-in device driver 70:0553 AUX Built-in device driver 70:0565 COM1 Built-in device driver 70:0577 COM2 Built-in device driver 70:0589 COM3 Built-in device driver 70:059B COM4 Built-in device driver 70:0602 CLOCK$ Built-in device driver 70:0645 CON Built-in device driver 70:0671 A:-D: Built-in device driver 126:0000 DR DOS 11B0h, 4,528 System 126:0048 NUL Built-in device driver 241:0000 DR DOS 20EE0h, 134,880 System 253:0000 EMMXXXX0 3880h, 14,464 Loadable device driver 5DC:0000 E: CB90h, 52,112 Loadable device driver (SStor) 1296:0000 CON 1020h, 4,128 Loadable device driver 1399:0000 F: 820h, 2,080 Loadable device driver 141C:0000 G:-J: C60h, 3,168 Loadable device driver 1543:0000 DR DOS 2800h, 10,240 20 Disk buffers 17C0:15C0 DR DOS DE0h, 3,552 DR DOS BIOS code 16FA:3000 DR DOS 9440h, 37,952 DR DOS kernel code 232F:0000 COMMAND 1590h, 5,520 Program 24A9:0000 COMMAND 80h, 128 Data 24B1:0000 AMOUSE C0h, 192 Environment 24BD:0000 DELWATCH 13D0h, 5,072 Program 25FA:0000 AMOUSE 16E0h, 5,856 Program 2768:0000 INSTALL C0h, 192 Environment 2774:0000 INSTALL 600h, 1,536 Program 27D4:0000 PRSWAP C0h, 192 Environment 27E0:0000 PRSWAP 180h, 384 Program 27F8:0000 NC B0h, 176 Environment 2803:0000 ——– 10h, 16 FREE 2804:0000 VSHIELD 66F0h, 26,352 Program 2E73:0000 NC 3270h, 12,912 Program 319A:0000 COMMAND C0h, 192 Data 31A6:0000 COMMAND 1590h, 5,520 Program 32FF:0000 COMMAND 110h, 272 Environment 3310:0000 MEM C0h, 192 Environment 331C:0000 MEM 13AE0h, 80,608 Program 46CA:0000 ——– 59360h, 365,408 FREE C000:0000 ——– 8000h, 32,768 ————- ROM C800:0000 ——– 2000h, 8,192 ————- ROM D400:0000 ——– 2000h, 8,192 ————- ROM E000:0000 EMS 10000h, 65,536 ———- EMS memory F000:0000 ——– 10000h, 65,536 ————- ROM Conventional memory 0h 10000h 20000h 30000h 40000h 50000h 60000h 70000h 0K 64K 128K 192K 256K 320K 384K 448K | | | | | | | | 2222222222222222222222222222222222222222222222222222222222222222 2222222222222222…………….11111…..1…..[[[[[[[[11111111 | | | | | | | 4 512K 576K 640K 704K 768K 832K 896K 960K 1MB 80000h 90000h A0000h B0000h C0000h D0000h E0000h F0000h 100000h Upper memory Key: 2=RAM 1=ROM 0=Shadow ROM [=EMS Memory Type BDD Total Bytes ( Kbytes ) DB DDD Available Conventional 655,360 ( 640K ) 446,192 ( 435K ) Extended 4,194,304 ( 4,096K ) 3,145,728 ( 3,072K ) EMS 671,744 ( 656K ) 212,992 ( 208K ) via AutoPilot 1.03a
#134963From: Brian BartlettMar 5, 1994 3:56 AM
Gayle, your continuing trials with AutoPilot still perplex me. Have you tried running Enforcer (without Quiet) to see what kind of hits are generated? It doesn't make sense since it runs on this bastard installation here just fine. "You do trust me, don't you? Of course you do." — "To Play the King" (BBC)
#135023From: Ron LegroMar 5, 1994 12:01 PM
Here's my A2386 config.sys followed by a partial MEM /A dump: SHELL=C:\COMMAND.COM C:\ /P /E:512 /MH device=c:\janus\EMM.SYS EXCLUDE=D000-DFFF FULLDISPLAY TEST SHOWOPTIONS DEVICE=C:\DRDOS\HIDOS.SYS HIDOS=ON BREAK=ON FILES=125 LASTDRIVE=E HISTORY= ON,256,ON COUNTRY=001,850,C:\DRDOS\COUNTRY.SYS HIBUFFERS = 40 HIDEVICE=D:\TOOLS\VSAFE.SYS /1+/2-/3+/4-/5-/6-/7+/8- [VIRUS CHECKER] < Conventional memory > 0h 10000h 20000h 30000h 40000h 50000h 60000h 70000h 0K 64K 128K 192K 256K 320K 384K 448K | | | | | | | | 222222222222222222222222222222222222222222222222222222222222222222 222222222222222222………….111111…..1….[[[[[[[[[[111111111 | | | | | | | | | 512K 576K 640K 704K 768K 832K 896K 960K 1MB 80000h 90000h A0000h B0000h C0000h D0000h E0000h F0000h 100000h < Upper memory > Key: 2=RAM 1=ROM 0=Shadow ROM [=EMS Memory Type Total Bytes ( Kbytes ) Available Conventional 654,336 ( 639K ) 616,432 ( 601K ) Upper 16,384 ( 16K ) 2,576 ( 2K ) High 65,520 ( 64K ) 8,240 ( 8K ) Extended 4,194,304 ( 4,096K ) 0 ( 0K ) Extended via XMS N/A 4,128,768 ( 4,032K ) EMS 671,744 ( 656K ) 262,144 ( 256K )
#135177From: Gayle Lee FairlessMar 6, 1994 8:42 PM
Ron, Thanks! Yours and Steve Kapplin's messages may help me to make better use of the bridgeboard memory! Sincerely, (Mr.) Gayle Lee Fairless 'Perfessor Fearless' from the Rocket City! via AutoPilot 1.03a