home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
DP Tool Club 15
/
CD_ASCQ_15_070894.iso
/
maj
/
2305
/
install.
< prev
next >
Wrap
Text File
|
1994-04-12
|
4KB
|
130 lines
(1) Hardware Requirements:
PC 386 or better. MSDOS 3.3 or higher.
I recommend a minimum of 8Mb for better performance.
Hard disk for swapping (virtual memory).
The following description is borrowed from DJGPP.
Supported Wares:
* Up to 128M of extended memory (expanded under VCPI)
* Up to 128M of disk space used for swapping
* SuperVGA up to 1280 x 1024.
* 80387
* XMS & VDISK memory allocation strategies
* VCPI programs, such as QEMM, DESQview, and 386MAX
* Windows, OS/2 (in DOS Box).
Features: 80387 emulator, 32-bit unix-ish environment, flat memory
model, SVGA graphics.
(2) Unpack package:
There are subdirectories in this package.
If you use PKUNZIP to unpack this package, make sure that you add the
'-d' switch.
(3) Installation:
***** Important *****
If you have used DISPLAY older than version 1.70, please delete all old
video drivers, go32.exe and emu387.
Don't use vesanew.grn because it doesn't work for GO32 1.11.
*********************
Video drivers, emu387 and go32.exe are borrowed from DJGPP and GRX.
+ This go32.exe is the original one from DJGPP 1.11.maint4.
1. Place GO32.EXE within system search path.
2. Video Driver Setup:
+ All video drivers are in the DRIVER subdirectory.
If you choose xxxxx.grn as video driver. add 'driver xxxxx.grn' to
environment GO32.
For example, go32=driver x:/xxxxx/xxxxx.grn
If you can't find any suitable driver for your video card or you want
to use VESA interface, there are two ways you can choose:
(a).
Just DON'T add anything to GO32. The default video driver in GO32 is
VESA driver.
For example, go32=
OR
(b).
+ Use vesa111.vdr.
+ For example, go32=driver x:/xxxxx/vesa111.vdr
For VESA user :
Please use vesainfo.com to check if your VGA BIOS supports VESA
standard.
+ I suggest that you try (a) first. If (a) doesn't work then try (b).
If your VESA BIOS works under PROTECTED mode, you can
+ add 'driver ::p' to GO32(for (a)) or
+ append '::p' to vesa111(for (b))
to speed up graphics operations.
+ For example, go32=driver ::p for (a)
+ go32=driver x:/xxxxx/vesa111.vdr::p for (b)
For DPMI(Windows, OS/2) user :
You must use VESA video driver.
3. 80x87 Emulator Setup:
If you do not have an 80x87, add 'emu x:/xxxxx/emu387' to GO32.
For example, go32=driver x:/xxxxx/xxxxx.grd emu x:/xxxxx/emu387
emu387 is included in this package.
For DPMI(Windows, OS/2) user :
You must have a REAL 80x87. Emulator doesn't work under DPMI.
4. Supress DPMI(for DOS user only):
If your memory manager supports both DPMI & VCPI(i.e. 387MAX), I suggest
that you add 'nodpmi' to GO32.
+ For Windows or OS/2 user :
+ You can't add 'nodpmi' to GO32.
+ If your memory manager supports both DPMI & VCPI and you are planning
+ to run DISPLAY under both DOS and Windows(OS/2), I suggest that you
+ disable the DPMI support in your memory manager. So you don't have to
+ keep two copies(one for DOS, supresses DPMI; one for Windows, enables
+ DPMI) of runme.bat.
5. Change Resources:
Please use a text editor to modify the configuration file, CONFIG.DIS.
You MUST change the SYSTEM section at least.
6. Run:
+ Read HINT.DOC.
Edit RUNME.BAT and use it to run DISPLAY.
(4) Notes:
1. For ALL user:
It is reported that DISPLAY is incompatible with emm386.sys from DR-DOS.
If you encounter this problem or you can run DISPLAY uner these systems
without problem, please give me an E-mail. Thanks.
2. For VESA user :
You can find VESA BIOS extension at:
wuarchive.wustl.edu: /mirrors/msdos/graphics
godzilla.cgl.rmit.oz.au: /kjb/MGL
3. For DPMI(Windows, OS/2) user :
DISPLAY doesn't support MOVIE playing in this mode. You can still save
movie frames.
Mouse is not supported.