Scrolling Window and Expanded Memory with Intel X86 (AREV Specific)
At 30 DEC 2004 03:20:12PM Ray Foster wrote:
Two Questions:
1) Am I out of luck to get expanded memory working with an Intel x86 machine/ how do I find out what my "chip set" is?
2) I am unable to see more in a window than shows - I have 50 items I would like to input into a window and can only see or access the first few. What to do?
I am runing AREV3.1 on a Windows 2000 Dell desktop (Dimension 4400.
Thanks
At 30 DEC 2004 05:45PM S Smith wrote:
Two Questions:
1) Am I out of luck to get expanded memory working with an Intel x86 machine/ how do I find out what my "chip set" is?
Dell and Compaq and HP often put their USB driver buffers and network card buffer addresses inside the memory region from 640 kB to 1mB - this is where AREV likes to set up its page frame address.
What you really need to do is examine the Windows Hardware device drivers (right click on My computer - Properties - Hardware - Device Manager and find out what is using segment register addresses immediately above A000h
2) I am unable to see more in a window than shows - I have 50 items I would like to input into a window and can only see or access the first few. What to do?
I am runing AREV3.1 on a Windows 2000 Dell desktop (Dimension 4400.
You can run in EGA 80*50 or 80*43 character mode by setting the shortcut that way and also setting AREV's max screen length to 50 rows.
Steve
At 31 DEC 2004 02:34PM Ray Foster wrote:
Screen size - Thank you Thank you - works great! I can now see 50 lines. There is no scroll on the entry screen as there is on the design screen. Any way to get the entry screen to scroll?
Mem - I looked through (not all!) the resources on the hardward device managers and did not find what was just above A000h. Two things are:
USB drivers uses EF40 - EF5F interrupt 19
Network card uses D400 - D4FF and FEAFEC00 - FEAFECFF interrupt 13
I also saw that the numeric data processors had no drivers installed with recources: 00F0 - 00FF and interrupt 13.
Where can I get a numeric data processor driver?
DOS mem /d shows:
Address Name Size Type
—— ——– —— ——000000 000400 Interrupt Vector000400 000100 ROM Communication Area000500 000200 DOS Communication Area000700 IO 000370 System DataCON System Device DriverAUX System Device DriverPRN System Device DriverCLOCK$ System Device DriverCOM1 System Device DriverLPT1 System Device DriverLPT2 System Device DriverLPT3 System Device DriverCOM2 System Device DriverCOM3 System Device DriverCOM4 System Device Driver000A70 MSDOS 001690 System Data002100 IO 0023D0 System DataKBD 000CD0 System ProgramHIMEM 0004E0 DEVICE=XMSXXXX0 Installed Device Driver000720 FILES=000090 FCBS=000240 LASTDRIVE=0007D0 STACKS=0044E0 COMMAND 000A20 Program004F10 MSDOS 000070 -- Free --004F90 COMMAND 000460 Environment005400 DOSX 0087A0 Program00DBB0 COMMAND 000380 Data00DF40 COMMAND 000A20 Program00E970 COMMAND 000360 Environment00ECE0 MEM 000370 Environment00F060 MEM 017550 Program0265C0 MSDOS 079A20 -- Free --09FFF0 SYSTEM 031000 System Program0D1000 IO 003100 System DataMOUSE 0030F0 System Program0D4110 MSDOS 000380 -- Free --0D44A0 MSCDEXNT 0001D0 Program0D4680 REDIR 000A70 Program0D5100 DOSX 000080 Data0D5190 MSDOS 00AE60 -- Free --655360 bytes total conventional memory655360 bytes available to MS-DOS593792 largest executable program size1048576 bytes total contiguous extended memory0 bytes available contiguous extended memory941056 bytes available XMS memoryMS-DOS resident in High Memory AreaThanks for your help.
RF
At 31 DEC 2004 05:15PM S Smith wrote:
USB drivers uses EF40 - EF5F interrupt 19
Network card uses D400 - D4FF and FEAFEC00 - FEAFECFF interrupt 13
Try disabling the network card (temporarily) then calling AREV with and the /XM1024 switch - maybe you can trick it into working.
I recall a recent post by Barry Stevens re Compaqs which led in this direction.
Steve
At 05 JAN 2005 10:55AM Ray Foster wrote:
Disabling the network card and calling AREV /XM1024 still shows expanded memory inactive on system information.
At 06 JAN 2005 04:20AM The Sprezzatura Group wrote:
There are some machines, no matter what you do, that just will not load up into EMS memory.
The only simply thing really left for you to try in this instance is to use the EMM command in the CONFIG.NT file.
<code> EMM=B=4000 RAM <code>
Take careful note of the spaces in the command line.
There are a few other options you can do. If your BIOS lets you, you can tell the BIOS not to use a plug and play OS. You can then go in and reconfigure the settings for your cards and move them to different areas of memory. What you'll need is 64K of memory in a single block between 640 and 1024 for EMS to allocate a full page frame.
If your BIOS does not allow this, then there are two other options available.
One is to reinstall your OS and tell it not to be a plug and play OS. That might let you reconfigure the memory settings, but there is no guarantee.
The other is to get a virtual machine running, which can run DOS. This is the solution I ended up with on my laptop. I used VMWare, created an MS DOS 6.22 VM, loaded Windows 3.11, and run AREV through there. I needed Windows 3.11 because I couldn't find network drivers that would run in pure DOS mode.
The network drivers are to allow you to map from the VM to the rest of the machine. So, I have my Revelation subdir mapped as X. All my systems then map to X and I access the software from there.
You might have better luck with FreeDOS or DOS32 or one of the other DOS alternatives out there, but for me doing the old DOS/Win3.1 was quick, fast and easy, and gives me full EMS memory (at the cost of some disk space for the VM). All in all, a fair trade, really.
The Sprezzatura Group
World Leaders in all things RevSoft