#memory setup
10 messages in this thread
Steven,
Merry Christmas! I'm now running DRDOS 6.0 on a 386 bridgeboard. I've
used SuperStor PRO on my D: drive on the hardcard.
Which memory manager is better: the one with DRDOS, or the one from
Janus? How should it be set?
My HP Deskjet 500C is doing fine! WordPerfect 6.0 for DOS works nicely
with it. The envelope option is also useful although I am still learning
my way around it. (I also have WordStar 7.0.)
Hope Florida is treating you right!
Season's greetings,
(Mr.) Gayle Lee Fairless
'Perfessor Fearless' from the Rocket City!
via AutoPilot 1.03a
Gayle,
my recommendation is to junk the one that came with Janus. I've
eliminated a lot of problems by upgrading to the one that came with
MS-DOS, so I'd suspect the same would be true of using the one that came
with DR-DOS.
Brian
bjbart@watserv.ucr.edu
Brian,
Thanks! I guess I need only exclude the memory that Janus uses.
Presently, I'm having to use a memory manager that works with a
separate 2 meg board that can be used as expanded memory. Once I take the
Rambank from DFI out, the possibly better memory manger could then be used
to advantage.
The 386 BB keeps coming up with an invalid configuration message. The
BB has 5 meg total on board.
Merry Christmas!
Sincerely,
(Mr.) Gayle Lee Fairless
'Perfessor Fearless' from the Rocket City!
via AutoPilot 1.03a
Brian,
I tried the one that came with DRDOS 6.0; it wouldn't install because
it couldn't find any 64 KB frames or something.
Fortunately, I had used a ? instead of REM to take out the old memory
manager. In DRDOS config.sys files the ? lets the operator answer a Y/N
question on whether to execute the line.
Happy New Year!
Sincerely,
(Mr.) Gayle Lee Fairless
'Perfessor Fearless' from the Rocket City!
DEVICE=\SSTORDRV.SYS
DEVICE=\DEVSWAP.COM
SHELL=C:\COMMAND.COM C:\ /P /E:512
BREAK=ON
HIBUFFERS=20
FILES=30
FCBS=4,4
FASTOPEN=256
LASTDRIVE=L
HISTORY=ON, 256, ON , OFF, OFF
COUNTRY=001,,C:\DRDOS\COUNTRY.SYS
HIDOS=ON
DEVICE=C:\DRDOS\EMM386.SYS /F=AUTO /K=2048 /B=FFFF /V /E=D000-DFFF /R=AUTO
HIDEVICE=C:\DRDOS\ANSI.SYS
ECHO The following lines are from your original CONFIG.SYS file.
ECHO You may wish to remove this statement and edit CONFIG.SYS to ECHO
remove duplicate lines and combine those that follow with
ECHO those that preceed this statement. We recommend that you use ECHO the
DR DOS EDITOR to make these modifications.
ECHO Enter 'N' for lines you wish to be ignored.
?DEVICE=C:\SYSTEM\EMS40.SYS /B=E000 /P=258
?DEVICE=C:\SYSTEM\EMSDISK.SYS 1024
DEVICE=C:\DRDOS\VDISK.SYS 1024 128 64 /E
HIDEVICE=C:\JANUS\JDISK.SYS
via AutoPilot 1.03a
Gayle,
one thing that immediately comes to mind concerning your config.sys
file is that everything I've ever read recommends that HIMEM.SYS, if used,
and EMM386.SYS must be in the first two lines of the config.sys. This is
in order to allow memory allocations to work properly. I'd put the EMS
driver next in line, then think about the rest of it.
Have you tried this? BTW, if your EMM and EMS drivers are on the
SuperStor partition, pull them out and place them on a non-compressed
partition. I keep hearing of problems over in IBM-land having them on the
compressed partition.
Brian
bjbart@watserv.ucr.edu
Gayle,
Merry Christmas, too!! I've been reading some of your messages, so I
knew you were getting things going. I take it the hard drive is no up and
running on the PC side?
Use the DRDOS EMM386.SYS manager. The Janus one is ONLY for EXPANDED
memory, not EXTENDED. You need EXTENDED to run windows and most of the newer
software. However, if you need EXPANDED memory the DRDOS memory manager can
set aside an EMM allocation. However, I would not use PC-Kwik for your disk
cache. Instead, you should buy HyperDisk. It's considerably faster as well as
more robust than PC-Kwik. You may also wish to consider using Stacker instead
of Superstor. For one thing Stacker drives can be easily uninstalled, whereas
Superstor drives cannot.
I just installed Norton Desktop for Windows 3.0, which is quite nice.
It just about makes Windows like OS/2 except, of course, I still have DRDOS
underneath. DRDOS 7.0 is apparently out or coming shortly. I'm anxious to see
what it's like and if it's still compatible with Janus software. OS/2 is not
at all compatible with Janus. Although OS/2 runs fine, you can't use AMOUSE,
AREAD, AWRITE, or JLINK. I played with it for awhile, then decided to move
back to ordinary Windows.
Have a good holiday, Gayle. I'm heading for Atlanta tomorrow evening
for the balance of the week to visit my father. Take care.
Steven,
By the time you read this, I guess I should say Happy New Year!
Ironically, you'll be physically closer to me in Alabama when you come up
to Atlanta. (This could make for some trivial paradoxes!)
As I told Brian, I have been using a 3rd-party memory manager because
it maps in the 2 meg Rambank from DFI. Now with 5 meg of its own, the BB
can probably do better w/o the Rambank and by using the DRDOS memory
mangaer.
Using the DRDOS manager could solve the invalid configuration message
that keeps coming up.
Happy New Year!
Sincerely,
(Mr.) Gayle Lee Fairless
'Perfessor Fearless' from the Rocket City!
via AutoPilot 1.03a
Gayle,
If the invalid configuration message is from the BB it means something
in your CMOS setup isn't set correctly. It may be you need to change the
amount of physical memory you have. Run BBsetup and check to see if the memory
and other settings conform with the actual BB and device setup you have hooked
up.
Happy New Year, too!!
Steve,
I sent a copy of my Config.sys to Brian to see if I'd made any
mistakes. I used the DRDOS 6.0 Setup utility to make the change after
saving the old versions. I compared the new and old versions with the FC
command (I suppose Comp would also work.) to see the differences. It
reminds of the Unix diff command for comparing files. Very handy!
I KNOW that I have only a total of 5 meg onboard. Anyway, I just now
(2220 Tues 28 Dec 93) found that I had told the system I had 2 meg in
extended memory offboard. However, that memory in my DFI Rambank is only
intended for expanded memory. Now there is no invalid configuration
message! (after setting the offboard extended memory to zero!) The
hardcard is set to NONE for both its harddrives (20M@: total, 40M).
But, I get the following from the DRDOS EMS386(sp?) memory handler:
EMM386: The driver can't install as there is no unused
64 Kb range available for memory management.
How was your Atlanta trip? With all the bad weather in Tennessee and
other places, we are probably going to visit much this year!
Sincerely,
(Mr.) Gayle Lee Fairless
'Perfessor Fearless' from the Rocket City!
ZD Address DBD Owner DDBD Size DDDDDDDDDDDBD Type
3 0:0000 3 ——– 3 A0000h, 655,360 3 ————- RAM
3 0:0000 3 ——– 3 400h, 1,024 3 Interrupt vectors
3 40:0000 3 ——– 3 100h, 256 3 ROM BIOS data area
3 50:0000 3 DR DOS 3 200h, 512 3 DOS data area
3 70:0000 3 DR BIOS 3 B60h, 2,912 3 Device drivers
3 70:050B 3 PRN 3 3 Built-in device driver 3
70:051D 3 LPT1 3 3 Built-in device driver 3
70:052F 3 LPT2 3 3 Built-in device driver 3
70:0541 3 LPT3 3 3 Built-in device driver 3
70:0553 3 AUX 3 3 Built-in device driver 3
70:0565 3 COM1 3 3 Built-in device driver 3
70:0577 3 COM2 3 3 Built-in device driver 3
70:0589 3 COM3 3 3 Built-in device driver 3
70:059B 3 COM4 3 3 Built-in device driver 3
70:0602 3 CLOCK$ 3 3 Built-in device driver 3
70:0645 3 CON 3 3 Built-in device driver 3
70:0671 3 A:-D: 3 3 Built-in device driver 3
126:0000 3 DR DOS 3 11B0h, 4,528 3 System
3 126:0048 3 NUL 3 3 Built-in device driver 3
241:0000 3 DR DOS 3 204D0h, 132,304 3 System
3 253:0000 3 E: 3 CB90h, 52,112 3 Loadable device driver 3
F0D:0000 3 CON 3 1020h, 4,128 3 Loadable device driver 3
1010:0000 3 EMMXXXX0 3 27E0h, 10,208 3 Loadable device driver 3
128F:0000 3 F: 3 650h, 1,616 3 Loadable device driver 3
12F5:0000 3 G: 3 820h, 2,080 3 Loadable device driver 3
1378:0000 3 H:-K: 3 C60h, 3,168 3 Loadable device driver 3
149F:0000 3 DR DOS 3 2800h, 10,240 3 20 Disk buffers
3 171F:15C0 3 DR DOS 3 DE0h, 3,552 3 DR DOS BIOS code
3 1659:3000 3 DR DOS 3 9440h, 37,952 3 DR DOS kernel code
3 228E:0000 3 COMMAND 3 1590h, 5,520 3 Program
3 23E7:0000 3 COMMAND 3 210h, 528 3 Environment
3 2408:0000 3 ——– 3 80h, 128 3 FREE
3 2410:0000 3 AMOUSE 3 F0h, 240 3 Environment
3 241F:0000 3 DELWATCH 3 13D0h, 5,072 3 Program
3 255C:0000 3 AMOUSE 3 16E0h, 5,856 3 Program
3 26CA:0000 3 INSTALL 3 F0h, 240 3 Environment
3 26D9:0000 3 INSTALL 3 600h, 1,536 3 Program
3 2739:0000 3 INSTALL 3 F0h, 240 3 Environment
3 2748:0000 3 VSHIELD 3 66F0h, 26,352 3 Program
3 2DB7:0000 3 INSTALL 3 600h, 1,536 3 Program
3 2E17:0000 3 PRSWAP 3 F0h, 240 3 Environment
3 2E26:0000 3 PRSWAP 3 180h, 384 3 Program
3 2E3E:0000 3 MEM 3 F0h, 240 3 Environment
3 2E4D:0000 3 MEM 3 13AE0h, 80,608 3 Program
3 41FB:0000 3 ——– 3 5E050h, 385,104 3 FREE
3 C800:0000 3 ——– 3 2000h, 8,192 3 ————- ROM —— 3
D400:0000 3 ——– 3 2000h, 8,192 3 ————- ROM —— 3
E000:0000 3 EMS 3 10000h, 65,536 3 ———- EMS memory — 3
F000:0000 3 ——– 3 10000h, 65,536 3 ————- ROM ——
3< D Conventional memory D>
0h 10000h 20000h 30000h 40000h 50000h 60000h 70000h
0K 64K 128K 192K 256K 320K 384K 448K
C | | | | | | |
2222222222222222222222222222222222222222222222222222222
222222222
2222222222222222………………..1…..1…..[[[[[[[
[11111111 | | | | | | |
| 4 512K 576K 640K 704K 768K 832K 896K
960K 1MB 80000h 90000h A0000h B0000h C0000h D0000h E0000h
F0000h 100000h > >3< Upper memory
>
Key: 2=RAM 1=ROM 0=Shadow ROM [=EMS
Z Memory Type DB Total Bytes ( Kbytes ) DB Available
D
Conventional 655,360 ( 640K ) 465,936 ( 455K
) Extended 4,194,304 ( 4,096K ) 3,145,728 (
3,072K ) EMS 2,097,152 ( 2,048K ) 983,040 (
960K )
via AutoPilot 1.03a
Gayle,
The memory manager message means that there isn't enough space in the
upper memory blocks to install the expanded memory window. The memory manager
needs a contiguous 16k block in which to install the emm window. Apparently,
you are using all of the memory or at least enough of upper memory to preclude
the block. You need to unload something. Run the DRDOS mem program to see how
much upper memory space is available.