#hardcard interrupts
6 messages in this thread
Steven,
The system was booted from a floppy in A: drive with the following
line:
DEVICE=A:\DRDOS\EMM386.SYS /F=NONE /K=0 /B=NONE /V /E=D000-DFFF /R=AUTO
The hardcard didn't respond properly, but everything else seemed to
work.
I called 800 information for Plus Development Corporation's number and
got Quantum. I left an order for a configuration card on the hardcard.
Now I guess it's just a matter of finding out how to rearrange the
interrupts to make proper use of DRDOS EMM386.SYS.
Got any ideas? I have Version 4.4 of SYSID which hangs the system when
used but printed out 14 pages anyway.
I'm also including the MEM printout that I got by using the floppy.
Sincerely,
(Mr.) Gayle Lee Fairless
'Perfessor Fearless' from the Rocket City!
Address Owner Size Type
0:0000 ——– A0000h, 655,360 ————- RAM ———-
0:0000 ——– 400h, 1,024 Interrupt vectors
40:0000 ——– 100h, 256 ROM BIOS ta area
50:0000 DR DOS 200h, 512 DOS ta area
70:0000 DR BIOS AD0h, 2,768 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:-B: Built-in device driver
11D:0000 DR DOS 11B0h, 4,528 System
11D:0048 NUL Built-in device driver
238:0000 DR DOS 11A90h, 72,336 System
246:0000 EMMQXXX0 660h, 1,632 Loadable device driver
2AD:0000 $ADDSTOR 5350h, 21,328 Loadable device driver
7E3:0000 C: 800h, 2,048 Loadable device driver
872:15C0 DR DOS DE0h, 3,552 DR DOS BIOS code
7AC:3000 DR DOS 9440h, 37,952 DR DOS kernel code
13E1:0000 COMMAND 210h, 528 Program
1402:0000 COMMAND 210h, 528 Environment
1423:0000 ——– 80h, 128 FREE
142B:0000 AMOUSE A0h, 160 Environment
1435:0000 AMOUSE 16E0h, 5,856 Program
15A3:0000 MEM A0h, 160 Environment
15AD:0000 MEM 13AE0h, 80,608 Program
295B:0000 ——– 76A50h, 485,968 FREE
C000:0000 ——– 8000h, 32,768 ————- ROM ——-
C800:0000 ——– 2000h, 8,192 ———- Shadow ROM —
CA00:0000 ——– 6000h, 24,576 ———- Upper RAM —-
CA00:0000 DR DOS 20A0h, 8,352 XMS Upper Memory Block
CC0A:0000 DR DOS 130h, 304 XMS Upper Memory Block
CC1D:0000 DR DOS 130h, 304 XMS Upper Memory Block
CC30:0000 DR DOS 20A0h, 8,352 XMS Upper Memory Block
CE3A:0000 DR DOS 1040h, 4,160 System
CE3C:0000 CON 1020h, 4,128 Loadable device driver
CF3E:0000 DR DOS 880h, 2,176 System
CF40:0000 D:-G: 860h, 2,144 Loadable device driver
CFC6:0000 DR DOS 390h, 912 System
CFFF:0000 EXCLUDED 17010h, 94,224 Upper system memory
D400:0000 ——– 2000h, 8,192 ————- ROM —
E000:0000 EMM386 7000h, 28,672 EMM386 device driver code
E700:0000 ——– 9000h, 36,864 ———- Upper RAM —
E700:0000 DR DOS 2660h, 9,824 System
E966:0000 DR DOS 20A0h, 8,352 XMS Upper Memory Block
EB70:0000 DR DOS 20A0h, 8,352 XMS Upper Memory Block
ED7A:0000 DR DOS 20A0h, 8,352 XMS Upper Memory Block
EF84:0000 DR DOS 7C0h, 1,984 System
F600:0000 ——– 1000h, 4,096 ———- Shadow ROM —
FFFF:00E0 COMMAND 1380h, 4,992 Program
FFFF:1470 ——– C250h, 49,744 FREE
FFFF:D6C0 DR DOS 2800h, 10,240 20 Disk buffers
Conventional memory
0h 10000h 20000h 30000h 40000h 50000h 60000h 70000h
0K 64K 128K 192K 256K 320K 384K 448K
| | | | | | | |
2222222222222222222222222222222222222222222222222222222222222222
2222222222222222…………….11110222..1……..2222…111111
| | | | | | | | |
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 655,360 ( 640K ) 566,720 ( 553K )
Upper 155,648 ( 152K ) 0 ( 0K )
High 65,520 ( 64K ) 49,744 ( 48K )
Extended 4,194,304 ( 4,096K ) 0 ( 0K )
Extended via XMS N/A 2,818,048 (2,752K )
via AutoPilot 1.03a
Gayle,
The only change I would suggest is to change the /E to /E=D000-D7FF.
You don't need to protect all the way up to DFFF because the Janus segment only
uses memory from D000-D7FF. You could also change /B to /B=AUTO, which will
relocate BDOS into the UMB, but not into himem. I suspect the problem may be
that the hard card is using a segment of memory which needs to be excluded.
Judging from the listing, that segment may be from C000-CFFF. You might try
/E=C000-CFFF,D000-D7FF and see if that helps. Perhaps EMM386.SYS isn't
detecting the hard card's controller and something gets overwritten. That's my
best guess right now.
Hi Steven,
Where did you get the info that Janus only uses D000-D7FF? My (admittedly old)
tech ref manual says D400-DFFF is used for "Disk buffer ram", divided between
byte access, graphic access and word access.
Marion
CROSSINGS
Newsletter for Amiga/PC/Mac compatibility
Marion,
If you run PCPrefs you find that the Janus memory segment choices are
D000 and A000. Normaly usage is D000. A check of memory allocation on the PC
side using DRDOS' MEM or the Windows memory utility indicates that the Janus
BIOS is allocated between D000 and D7FF. I found nothing in the Docs for the
BB which specified the range, so I was going by what I could find snooping in
memory. My 386 BB reference doesn't actually provide any specific information
other than the starting address.
Steven,
Earlier Bridgeboard manuals specified the entire 64K block. I have a feeling
that the reason memory utilities don't see the whole block is that it's not in
use until it's actually used, for data transfer, etc.
People who don't block off the whole 64K do seem to run into problems, I've
noticed.
Marion
CROSSINGS
Newsletter for Amiga/PC/Mac compatibility
Marion,
I wonder if that's also true with the 386 BB or only the earlier ones.
Although I haven't yet had any evidence of such a problem, it could still be a
potential problem, I'm sure. Possibly DRDOS's memory manager bypasses the
whole block, I'm not sure. I only exclude the first half of the block
explicitly, although for a long while I didn't exclude it at all, but never had
any problems. I excluded it when I started to have some problems with AMOUSE
not installing properly and thought it might have had something to do with the
Janus segment. Turned out it was a problem with Janus.library not installing
properly, but I never changed my config.sys, since the exclusion didn't seem to
affect anything adversely.