Detailed Contents
Preface
1 Microsoft Language Utilities
2 Board Installation
3 Operating System Setup
4 Installing Software
5 Configuration Utility
6 Setting up the Video Tape Recorder
7 Other Software
8 Other Hardware
This section details the setting up of the MS-DOS, Windows 3.1 or Windows 95/98 environment so that DigImage is able to access the resources it requires. It is strongly recommended that Windows 95/98 is used on all newer machines. Future releases of DigImage may not operate correctly in the older environments.
Create a base directory on your hard drive to contain the DigImage files (e.g. C:\DIGIMAGE). The installation procedure will create a number of subdirectories within this directory in which the various parts of the DigImage system will be located. Included among these is a subdirectory BIN. The complete path specification for this directory (i.e. C:\DIGIMAGE\BIN) must be added to PATH within your C:\AUTOEXEC.BAT so that MS-DOS is able to find the DigImage executable files.
In addition, DigImage requires an environment variable DIGIMAGE to point to the base directory you have created (i.e. C:\DIGIMAGE). This should be specified in your C:\AUTOEXEC.BAT by adding a line of the form
SET DIGIMAGE=C:\DigImage
DigImage uses this variable to find the various components of the system.
With versions of DigImage prior to 1.5 it was recommended that a RAM disk was utilised for temporary files. However, due to changes in the way DigImage uses overlays and improvements in disk caching software, the use of a RAM disk is no longer recommended. It is very strongly recommended that you do not use a RAM disk if you are operating under Windows 95/98.
If you still wish to use a RAM disk (perhaps for other purposes) and wish DigImage to be aware of it and make use of it, then ensure that you have a line of the form
SET RAMDISK=D:
in your AUTOEXEC.BAT. We would advise, however, that any such RAM disk is at least 1MByte in size and that you do not use one when running under Windows unless you have at least 16MBytes of RAM installed. Refer to sample AUTOEXEC.BAT for further details.
The environment variable VIDEO is used to communicate the type of video recorder to be used by DigImage. VIDEO should be set in C:\AUTOEXEC.BAT to one of the following:
AG7330 For Panasonic AG-7330 VTRs
AG7350 For Panasonic AG-7350 VTRs
BRS822 For JVC BRS-822 VTRs
NOVIDE No modified RS232 controlled video
At times during its operation, DigImage needs to create a number of temporary files. Generally these files will be deleted when they are no longer required. By default DigImage will utilise the directory %DIGIMAGE%\TMP (i.e. C:\DIGIMAGE\TMP) to contain these files. However, if the environment variable TMP has been declared in your C:\AUTOEXEC.BAT, then the directory pointed to by this variable will be used instead. If you wish this to point to a RAM disk (see comments in section 3.2 ) then you should ensure at least 1MByte of RAM is available.
A typical CONFIG.SYS and AUTOEXEC.BAT is listed below. Copies of these files may be found in the DigImage\Document directory as CONFIG.DOC and AUTOEXEC.DOC. It will be necessary to make minor adjustments to these files for most installations. We recommend, however, that you follow the same basic configuration. Refer to the next subsection if you are installing DigImage under Windows 95/98.
Typically you will copy these files into your root directory and then make the minor adjustments necessary to match your computer hardware. Once you have done this you would run MEMMAKER to optimise the use of the Upper Memory Blocks (UMBs) and so make more basic DOS memory available. During the MEMMAKER session, select the boot option which uses the most number of extended memory buffers and the minimum hardware configuration you will be using.
Once MEMMAKER has finished, you should have close to 600K of DOS memory available. If there is less than around 540K DigImage may not be able to run. If there is too little memory, use MSD (Microsoft Diagnostic) to examine the memory map. Try including those blocks marked "possible available" (indicated by a period in the memory map) in the EMM386 list in CONFIG.SYS. You may need to iterate a few times to determine which blocks are really available and which cause conflicts with other hardware. Once you have changed the I=... switches for EMM386 then run MEMMAKER again to re-optimise the use of the UMBs.
You will notice that MEMMAKER moves the HIMEM.SYS and EMM386.EXE statements to the top of CONFIG.SYS. Once you are satisfied with the memory arrangement, you will need to move them back to where they were originally and re-activate the HIMEM.SYS statements MEMMAKER has diabled (in the other boot options).
CONFIG.SYS for MS-DOS and Windows 3.1x:
rem ********************************************************************rem ** Config.Sys for MS-DOS and Windows 3.1x **rem ** ************************************** **rem ** **rem ** This file contains a sample Config.SYS file for DigImage **rem ** when running under MS-DOS and/or Windows 3.1x. For operation **rem ** under Windows 95, please refer to Document\Config95.TXT. **rem ********************************************************************rem ====================================================================rem = Configuration menu =rem = DigImage21 Set up for 21 EM buffers and no CD Rom. May be =rem = used for Windows if 16+MByte RAM installed. =rem = DigImage8 Set up for 8 EM buffers and no CD Rom. May be =rem = used for Windows if 8+MByte RAM installed. =rem = Windows Set up for DPMI EM buffers under Windows. =rem = No CD. =rem = WindowsCD Set up for CD operation. Only DPMI EM buffers. =rem ====================================================================[Menu]MenuColor=15,1MenuDefault=DigImage21MenuItem=DigImage21 DigImage with 21 EM buffers (no CD)MenuItem=DigImage8 DigImage with 8 EM buffers (no CD)MenuItem=Windows Windows (DPMI buffers, no CD)MenuItem=WindowsCD Windows (DPMI buffers, CD)rem ====================================================================rem = Memory for EM buffers =rem = Under most circumstances, installations of DigImage will wish =rem = to make use of some of the computer's own memory for image =rem = buffers in addition to those available on the frame grabber =rem = card. There are two fundamental ways in which this memory may =rem = be made available to DigImage. Under the first, some of the =rem = computer's RAM is reserved for the sole use of DigImage, while =rem = under the second, DigImage requests memory when it starts and =rem = frees it when it exits. Both options have their advantages. At =rem = present, however, the second option is available only when =rem = running under Windows (3.x or 95). =rem = =rem = Reserving memory at boot time - /INT15= =rem = Memory may be reserved at boot time for use by DigImage in =rem = both DOS and Windows. This memory is obtained by the addition =rem = of the /INT15= switch to the HIMEM.SYS statement in =rem = CONFIG.SYS. Unless there is another application which also =rem = makes use of memory reserved in this way (this is fairly =rem = unlikely), then the contents of the extended memory buffers =rem = will be preserved from one invocation of DigImage to the next =rem = until the computer is turned off or rebooted. =rem = =rem = The main drawback of this method of allocating memory is that =rem = this mememory is not available for other applications even =rem = when DigImage is not running. =rem = =rem = Allocating memory at runtime =rem = Under this scenario DigImage requests memory for the =rem = additional image buffers each time DigImage (or one of its =rem = components) is started. This memory is provided by the =rem = operating system, and returned to the operating system when =rem = you leave DigImage. Thus the memory is available for use by =rem = other applications when DigImage is not running. =rem = =rem = To use this form of memory allocation, do NOT include the =rem = /INT15= switch and make the appropriate selection in =rem = CONFIGUR.EXE. Note that at present this form of memory =rem = allocation is available only when DigImage is running =rem = under a DPMI server such as Windows (3.x or 95). =rem = =rem = A consequence of the memory being reused is that the =rem = contents of the image buffers will be lost if another =rem = application uses some or all of the memory. Normally this =rem = will not be a problem, but it may sometimes be inconvenient. =rem = =rem = From version 2.0 DigImage provides the capacity to save all =rem = the images to hard disk when you leave DigImage and restore =rem = them when you start again in that directory. While this =rem = may be a convenient feature, it requires up to 8MBytes of =rem = memory either in a single central file common to all =rem = directories in which DigImage is started, or a local file in =rem = each directory where you use this feature from. Refer to =rem = [X Procedure on quitting] under CONFIGUR.EXE for further =rem = details. =rem = =rem = Number of buffers available =rem = Under DOS, the number of buffers available is determined by =rem = the smaller of the number dictated by the available memory =rem = reserved by /INT15= and the maximum number set in CONFIGUR. =rem = =rem = Under Windows 3.x or Window 95, the number of buffers is =rem = always taken from the setting in CONFIGUR. If you are using =rem = memory allocated with /INT15= you MUST ensure the number of =rem = buffers specified does not exceed the amount of memory you =rem = have reserved. (If you are using memory allocated dynamically =rem = at run time, then you should restrict the CONFIGUR setting to =rem = be a reasonable value.) =rem = =rem ====================================================================[DigImage21]rem DigImage with 21 EM buffersset BootOption=DigImage21DEVICE=C:\DOS\HIMEM.SYS /int15=5440[DigImage8]rem DigImage with 8 EM buffersset BootOption=DigImage8DEVICE=C:\DOS\HIMEM.SYS /int15=2112[Windows]rem DPMI buffers available under Windows 3.xset BootOption=WindowsDEVICE=C:\DOS\HIMEM.SYS[WindowsCD]rem DPMI buffers available under Windows 3.xrem CD Rom installedset BootOption=WindowsCDDEVICE=C:\DOS\HIMEM.SYS[Common]rem ====================================================================rem = EMM386.EXE =rem = Install memory management to free up memory in the first 640K. =rem = At times DigImage can be very greedy on memory, so you should =rem = ensure as much upper memory (UMB) is available as possible. =rem = One way of determining which blocks of memory between 640K and =rem = 1MByte may be available is to run MSD (Microsoft Diagnostic) =rem = and try including everything that it says is available or =rem = is possibly available. If you specify something with the I= =rem = switch when it is not available, then your machine will =rem = probably not boot up correctly. In this case, bypass =rem = CONFIG.SYS and remove the offending switch. =rem = =rem = If you have an ethernet card then it is likely that MSD will =rem = report the ethernet card's RAM window as available when in =rem = fact it requires the X= exclusion switch for EMM386. =rem = =rem = In some cases you might be able to rely on MEMMAKER and EMM386 =rem = to determine which blocks of memory are available. However, =rem = our experience suggests that there is often much more memory =rem = available than reported by either of these. =rem = =rem = If things remain tight, then it may be possible to shift some =rem = of the hardware addresses around (e.g. an ethernet card RAM =rem = window) in order to make a smaller number of larger memory =rem = blocks available. MEMMAKER should then be able to fill these =rem = more efficiently. =rem = =rem = After all the switches are set up for EMM386 and Config.SYS =rem = and AutoExec.BAT have been taylored to suit your environment, =rem = run MEMMAKER in CUSTOM mode. Specify no expanded memory and =rem = no optimisation for Windows. All other controls should be =rem = "yes". As MEMMAKER prompts for which programs to put in =rem = extended memory, think about how the computer will be used. =rem = Only allow those drivers which will always be required to =rem = be included in the optimisation. In these examples you would =rem = not include the CDRom drivers as they are only used in the =rem = non-DigImage option. =rem = =rem = Note that after you have run MEMMAKER it will probably be =rem = necessary to reorganise this file back to its original form =rem = (retaining the DEVICEHIGH location switches) as MEMMAKER moves =rem = the HIMEM.SYS and EMM386.SYS lines to the top of the file, =rem = ignoring the possibility of there being more than one boot =rem = configuration of these. =rem = =rem = If you are running a WFW (Windows for Workgroups 3.11) network =rem = from DOS (i.e. you use the Windows\NET START command, then =rem = DO NOT include this in the optimisation. It will automatically =rem = load into the UMBs if there is space available. If you specify =rem = it in the optimisation then you will actually end up with less =rem = space! =rem = =rem = You will see in the example one that I have not tried moving =rem = BIOSes or the Ethernet RAM window to defragment the UMBs. The =rem = first of the I= switches (I=B000-B7FF) says to use the VGA =rem = monochrome memory area. As most displays ar colour these days, =rem = this is pretty safe for DOS, but may cause a problem with some =rem = Windows display drivers. All the other I= switches were set =rem = from the information returned by MSD and represent areas of =rem = memory available but which EMM386 and MEMMAKER could not find =rem = by themselves. =rem = =rem = There are two X= exlude switches. One (CC00-CFFF) is for the =rem = Ethernet card (a SMC Elite Ultra), and the other for one of =rem = the BIOSes (I can't remember if its the ATI video card or the =rem = Adaptec SCSI controller, not that it matters. =rem ====================================================================DEVICE=C:\DOS\EMM386.EXE NOEMS HIGHSCAN I=B000-B7FF I=D400-D7FF I=E800-EBFF X=CC00-CFFF X=D300-D3FFrem ====================================================================rem = Locate and set up DOS =rem ====================================================================DOS=HIGH,UMBBREAK=ONSHELL=C:\DOS\COMMAND.COM C:\DOS\ /E:768 /pBuffers=10,0Files=60DOS=UMBLastDrive=ZFCBS=16,0Stacks=0,0rem ********************************************************************rem ** Set up devices **rem ********************************************************************rem ====================================================================rem = SCSI controller =rem = Typically IDE drives do not require a driver. Some SCSI drive =rem = controllers require a driver to control the C: drive (e.g. =rem = BusLogic, UltraStor) while others only need them for things =rem = like Magneto-Optical drives and CD Roms (e.g. Adaptec). =rem = =rem = The computer on which this example was produced (a Gateway =rem = P5-90) has an Adaptec PCI SCSI controller for the hard disk =rem = and an IDE controller for the CDRom. The SCSI controller also =rem = controls a Magneto-Optical drive, thus requiring an additional =rem = driver to provide the standard interface layer (ASPI). For =rem = some controllers this driver must be loaded before EMM386 but =rem = for most loading after allows the driver to be loaded in =rem = extended memory. =rem ====================================================================DEVICEHIGH=C:\SYS\ADAPTEC\ASPI8DOS.SYS /Drem ====================================================================rem = RamDisk =rem = For DigImage version 1.x the use of a RAM Disk was recommended =rem = as this improved the performance of the particle tracking. =rem = However, due to improvements in the more recent versions of =rem = SmartDrv, the introduction of Dynamic Overlays to DigImage =rem = (which allow DigImage to run faster if more memory is =rem = available in the first 640K), and the general need to recover =rem = more of the first 640K to allow operation under Windows, we =rem = recommend a RAM Disk is nolonger used. If a RamDisk is still =rem = available, DigImage will use it provided the environment =rem = variable %RamDisk% points to it. =rem = =rem = The order in which this and the Magneto-Optical drives are =rem = specified in Config.SYS determines the letter assigned to the =rem = drive. =rem ====================================================================rem DEVICEHIGH=C:\DOS\RamDrive.sys 1216 128 8 /Erem ====================================================================rem = Disk drive =rem = Here we load any other drivers required for controlling disk =rem = drives etc. In this case there is a M-O drive on the SCSI =rem = controller (giving the Adaptec driver) and a CDRom on the =rem = IDE controller (an NEC device). The CDRom driver is loaded =rem = only if the machine is booted for WindowsCD. =rem ====================================================================DEVICEHIGH=C:\SYS\ADAPTEC\ASPIDISK.SYS /D[WindowsCD]DEVICE=C:\SYS\CDROM\MTMCDAI.SYS /D:MTMIDE01[Common]rem ====================================================================rem = Display card =rem = DigImage utilises standard ANSI control sequences for =rem = controlling screen format and colour at a Fortran level. =rem = If there was a replacement driver supplied with your VGA card =rem = then use this in preference to the standard DOS one as it is =rem = bound to be better and require less RAM. Here we are using an =rem = Orchid driver (although the display card is ATI). =rem ====================================================================rem DeviceHigh=C:\DOS\Ansi.SYSDEVICEHIGH=C:\SYS\VGA\EANSI.SYSrem ====================================================================rem = Country specific information (UK) =rem ====================================================================COUNTRY=44,,C:\DOS\COUNTRY.SYSrem ====================================================================rem = Other drivers =rem = IFSHLP.SYS 32 bit disk access for Windows 3.x. Needed if =rem = you are running a WFW network from DOS, so may =rem = as well include it in all boot options. =rem = =rem = POWER.EXE Power management. May cause problems on some =rem = machines. Not essential, so include only if =rem = you have memory to spare! =rem = =rem = This is NOT needed for Windows 95. =rem = =rem ====================================================================DEVICEHIGH=C:\SYS\WINDOWS\IFSHLP.SYSrem DEVICEHIGH=C:\DOS\POWER.EXE
AUTOEXEC.BAT for MS-DOS and Windows 3.1x:
@ECHO Offrem ********************************************************************rem ** AutoExec.Sys for MS-DOS and Windows 3.1x **rem ** **************************************** **rem ** **rem ** This file contains a sample AutoExec.BAT file for DigImage **rem ** when running under MS-DOS and/or Windows 3.1x. For operation **rem ** under Windows 95, please refer to Document\AutoEx95.TXT. **rem ********************************************************************rem ********************************************************************rem ** Basic MS-DOS set up **rem ********************************************************************VERIFY OFFPROMPT $P$GVERrem ********************************************************************rem ** Environment Variables **rem ********************************************************************rem ====================================================================rem = MS-DOS settings =rem ====================================================================set DIRCMD=/orem ====================================================================rem = DigImage pointers =rem = ----------------- =rem = DigImage =rem = This should point to the directory in which DigImage is =rem = installed. =rem = Video =rem = This should indicate the type of video recorder being =rem = controlled by DigImage. The supported options are: =rem = AG7330 Older Panasonic SVHS =rem = AG7350 Newer Panasonic SVHS =rem = BRS822 Expensive JVC SVHS =rem = RamDisk =rem = For DigImage version 1.x the use of a RAM Disk was recommended =rem = as this improved the performance of the particle tracking. =rem = However, due to improvements in the more recent versions of =rem = SmartDrv, the introduction of Dynamic Overlays to DigImage =rem = (which allow DigImage to run faster if more memory is =rem = available in the first 640K), and the general need to recover =rem = more of the first 640K to allow operation under Windows, we =rem = recommend a RAM Disk is nolonger used. If a RamDisk is still =rem = available, DigImage will use it provided the environment =rem = variable %RamDisk% points to it. =rem ====================================================================set DigImage=C:\Img\DigImageset Video=AG7350rem set RamDisk=D:rem ====================================================================rem = Disk Driver pointers =rem = -------------------- =rem = On our systems these variables are used by standard batch =rem = files on a number of different machines with different =rem = configurations and drive assignments. They provide a standard =rem = way of accessing a particular device, or detecting if such a =rem = device is present. =rem = OptDisk =rem = Points to the Magneto-Optical disk drive. =rem = CDRom =rem = Points to the CDRom drive. Note that this will only be present =rem = under the WindowsCD boot option in Config.SYS, so it should =rem = only be assigned a value under that option. =rem = NetDisk =rem = Points to a networked disk drive I always connect to (my =rem = Laptop) =rem = Server =rem = Points to the network file server (there will be one soon, I =rem = hope!). =rem ====================================================================if "%RamDisk%"=="" set OptDisk=D:if not "%RamDisk%"=="" set OptDisk=E:if "%BootOption%"=="WindowsCD" set CDRom=F:set NetDisk=G:set Server=Z:rem ====================================================================rem = Directory pointers =rem = ------------------ =rem = These environment variables are required by various pieces of =rem = software to locate specific files or directories. =rem = Lib =rem = Specifies where to search for language libraries. =rem = Tmp =rem = Directory for temporary files. Required by Microsoft languages =rem = (e.g. Fortran 77) and DigImage. If a RAM Disk exists, then =rem = things may be slightly faster if the TMP directory is on the =rem = RAM Disk (the directory will then need to be created each time =rem = the computer is rebooted). =rem = Temp =rem = Directory for temporary files. Required by Windows and various =rem = other applications. =rem ====================================================================set Lib=C:\Libif "%RamDisk%"=="" goto NoRDisk set Tmp=%RamDisk%\Tmp md %Tmp%goto Both:NoRDisk set Tmp=C:\Tmp:Bothset Temp=C:\Tmprem ====================================================================rem = Computer and user name are useful for DOS Batch files =rem = "Moana" = Maori for "Sea". My laptop is called "Hauiti" = =rem = "Light breeze" and my desktop at home is "Maui" who was the =rem = god who caught the fish (the North Island) from the canoe (the =rem = South Island) and so created New Zealand. =rem ====================================================================set CompName=Moanaset UserName=Stuart Dalzielrem ********************************************************************rem ** Disk Access **rem ********************************************************************rem ====================================================================rem = Disk cache =rem = It is essential that some form of disk caching is available to =rem = boost the speed of disk transfers. In the absence of a caching =rem = controller, SmartDrv provides more than adequate performance. =rem = For optimum performance it is desirable to cache both reads =rem = and writes. This may be done for both fixed drives and =rem = removable media such as Magneto-Optical drives (not floppy =rem = drives). You must take care, however, to only remove the disk =rem = once you are sure the cache is written out. For DOS 6.x it is =rem = sufficient to wait until DOS has returned to the C:\> prompt. =rem = For version 5.x you should issue SMARTDRV /C to flush the =rem = cache. =rem = =rem = Unfortunately SmartDrv does not allow colons (:) on the drive =rem = specification so it is not possible to use our environment =rem = variables for the M-O drive. =rem = =rem = The size of cache you specify depends on how much extended =rem = memory you have available and whether or not you are using =rem = a RAM drive. Below suggested values are given for the cache =rem = size with the /INT15= settings in Config.SYS: =rem = Buffers RAM /INT15= SmartDrv RamDisk Windows =rem = 21 8MByte 5440 512 1216 No =rem = 21 8MByte 5440 704 - No =rem = 21 16MByte 5440 1024 1280 Yes =rem = 21 16MByte 5440 2048 - Yes =rem = 8 8MByte 2112 512 1216 Yes =rem = 8 8MByte 2112 1536 - Yes =rem = 8 16MByte 2112 1024 1280 Yes =rem = 8 16MByte 2112 2048 - Yes =rem = =rem = If you are running exclusively under Windows, then you do not =rem = need the /INT15= switch as you can let DPMI supply the memory =rem = for the EM buffers. You should, however, set the cache size in =rem = a similar manner to ensure memory is available for the =rem = buffers. =rem = =rem = With some SCSI controllers it may be necessary to have =rem = SMARTDRV /DOUBLEBUFFER in Config.SYS in addition to the entry =rem = here. Consult your MS-DOS documentation for further details. =rem ====================================================================if "%OptDisk%"=="" LoadHigh C:\DOS\SMARTDRV.EXE C+ 2048 128if not "%OptDisk%"=="" LoadHigh C:\DOS\SMARTDRV.EXE C+D+ 2048 128rem ====================================================================rem = CDRom =rem = Only load driver if booting with it. Can detect this either =rem = with %BootOption% set to WindowsCD or by %CDRom% existing. We =rem = shall use the latter method to reduce the number of places =rem = changes would have to be made if the strategy changed. =rem = =rem = As this is not used in all boot options, it would be wasteful =rem = to load it into upper memory. =rem = =rem = By explicitly specifying the drive letter, we can enforce a =rem = constant letter across a range of different machines. =rem = Unfortunately MSCDEX does not like a colon after the drive =rem = letter so we can not use %CDROM%. =rem ====================================================================if not "%CDRom%"=="" C:\Dos\MSCDEX.EXE /D:MTMIDE01 /M:10 /L:Frem ====================================================================rem = Memory resident utilities and drivers =rem = ------------------------------------- =rem = DosKey =rem = Provides memory and editting functions at the DOS command =rem = prompt. =rem = KeyB =rem = Ensures the correct keyboard layout (101 key US, 102 key UK, =rem = etc.) is used. =rem = Share =rem = Looks after file sharing. Windows insists on this even if you =rem = don't explicitly use it. =rem ====================================================================LoadHigh C:\DOS\DosKey.COM /insertLoadHigh C:\DOS\KeyB UK,,C:\DOS\KEYBOARD.SYS /ID:166LoadHigh C:\Dos\Share.EXE /l:500 /f:5100rem ====================================================================rem = Mouse =rem = The decision on whether to load a DOS mouse driver is not =rem = straight forward. =rem = For: =rem = Some DOS applications make use of the mouse, if available. =rem = DigImage can use it for moving the cursor, sizing windows and =rem = drawing. =rem = Against: =rem = A DOS mouse driver is not required for Windows, the only =rem = application where a mouse is essential. =rem = Some mouse drivers take up a lot of space. =rem = There can be serial port conflicts if a serial mouse (rather =rem = than a bus mouse) is used. =rem = =rem = Here we shall not load the mouse. If needed, it can always be =rem = loaded from the DOS prompt. =rem ====================================================================rem Set Mouse=C:\Devices\MSMouserem LoadHigh C:\Devices\MSMouse\Mouserem ====================================================================rem = Paths and path variables =rem = This will differ, depending on your precise machine setup. In =rem = my case many things are pointed to by batch files in C:\BATCH =rem = rather than included explicitly on the path. The DIGIMAGE\BIN =rem = directory need not be on the path if you are only using code =rem = linked with the dynamic overlay linker. If you are using the =rem = older static overlay technology, then DIGIMAGE\BIN must be =rem = on the path. (If DIGIMAGE\BIN is not on the path, then there =rem = must be batch files somewhere on the path pointing to the =rem = appropriate executables.) =rem = =rem = If a RAM disk is being used, then it should be located on the =rem = path before DIGIMAGE\BIN, and a Bin directory created in it. =rem ====================================================================PATH C:\BATCH;C:\SYS\WINDOWS;C:\DOS;C:\BIN;%DigImage%\BINif not "%RamDisk%"=="" Path %RamDisk%\Bin;%Path%if not "%RamDisk%"=="" md %RamDisk%\Binrem ====================================================================rem = Network =rem = The final standard bit of setting up is starting the network. =rem = Here we are using Windows for Workgroups running TCPIP as =rem = the default protocol with NETBUEi in reserve. Note that by =rem = starting the network from DOS you must stop the network (using =rem = NET STOP) before starting Windows. This is most conveniently =rem = done by having a batch file to start Windows (hence the reason =rem = C:\BATCH was before C:\SYS\WINDOWS in the PATH specification. =rem = =rem = If you are lucky there is still some UMB left and so the =rem = network protocol manager, ethernet card driver and DOS =rem = redirector will all load high. They will do so automatically =rem = if there is space, so there is no need to LoadHigh the Net =rem = command. In fact, if you use LoadHigh then you will end up =rem = with less memory to play with! We only start the basic =rem = redirector (which is more than adequate) as it takes much less =rem = space than the full redirector. =rem ====================================================================C:\Sys\Windows\Net Start Basicrem !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!rem !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!rem !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!rem ********************************************************************rem ** Other Settings **rem ** These are specific to my machines and will not be required **rem ** elsewhere, although you may have other stuff you want to put **rem ** here instead. If possible, try to avoid things that steal **rem ** memory permanently! **rem ********************************************************************rem ====================================================================rem = MultiEdit =rem = Set default mode =rem ====================================================================set ME_Line=/X132 /Y44set ME_Mode=51rem ====================================================================rem = Environment variables for LiPS system =rem ====================================================================rem set f77=c:\bin\flrem set link=c:\bin\linkrem set f77lib=c:\bin\librem set make=c:\bin\nmakerem ====================================================================rem = Printer driver =rem ====================================================================rem C:\Sys\Printer\MltShare\MShare.EXE 11rem ====================================================================rem = GhostScript =rem ====================================================================Set GS_Lib=C:\Sys\Printer\GhostScr\GS3.51;C:\Sys\Printer\GhostScr\Fontsrem ====================================================================rem = Virus protection =rem ====================================================================echo.echo Virus check...Choice /C:YN /T:Y,10 Scan for changed filesif ErrorLevel 2 Goto DontScanC:\Sys\Virus\TK6_67\ViVerify C: /asm /n=5 < c:\sys\virus\tk6_67\me.txt:DontScan
A typical CONFIG.SYS and AUTOEXEC.BAT for use with Windows 95 or Windows 98 is listed below. Copies of these files may be found in the DigImage\Document directory as CONFIG95.DOC and AUTOEX95.DOC. It will be necessary to make minor adjustments to these files for some installations. We recommend, however, that you follow the same basic configuration. Refer to the previous subsection if you are installing DigImage under MS-DOS and/or Windows 3.1x.
CONFIG.SYS for Windows 95:
rem ********************************************************************rem ** Config.SYS for Windows 95/98 **rem ** **************************** **rem ** **rem ** This file contains a sample Config.SYS file for DigImage **rem ** when running under Windows 95/98. For operation under MS-DOS **rem ** and/or Windows 3.1x, please refer to Document\Config.TXT. **rem ********************************************************************rem ====================================================================rem = Configuration menu =rem = DigImage21 Set up for 21 EM buffers. You should have at =rem = least 16MBytes of RAM installed. =rem = DigImage8 Set up for 8 EM buffers. You should have at =rem = least 8MBytes of RAM installed. =rem = Windows Set up with no /INT15 buffers. Can use the =rem = onboard buffers and DPMI buffers (if DigImage =rem = appropriately configured. =rem = WARNING: DPMI buffers do not function correctly under =rem = Windows 95/98 =rem ====================================================================[Menu]MenuColor=15,1MenuDefault=DigImage21MenuItem=DigImage21 DigImage with 21 EM buffersMenuItem=DigImage8 DigImage with 8 EM buffersMenuItem=Windows Windows onlyrem ====================================================================rem = Reserve space for EM buffers =rem ====================================================================[DigImage21]rem DigImage with 21 EM buffersDEVICE=C:\Windows\HiMEM.SYS /int15=5440set BootOption=DigImage21[DigImage8]rem DigImage with 8 EM buffersDEVICE=C:\Windows\HiMEM.SYS /int15=2112set BootOption=DigImage8[Windows]rem No EM BuffersDEVICE=C:\Windows\HiMEM.SYSset BootOption=Windows[Common]rem ====================================================================rem = EMM386.EXE =rem = Install memory management to free up memory in the first 640K. =rem = At times DigImage can be very greedy on memory, so you should =rem = ensure as much upper memory (UMB) is available as possible. =rem = =rem = Windows 95/98 appears to be reasonably good about determining =rem = which bit of upper memory can be used. Normally you can leave =rem = the allocation to it. However, if you have insufficient memory =rem = available to run DigImage, you may wish to refer to the notes =rem = about EMM386 and MEMMAKER in the DOS version of CONFIG.SYS =rem = (found as DigImage\Document\Config.TXT). =rem = =rem = For most machines MEM should report around 600K of free memory =rem = at the DOS prompt. =rem ====================================================================DEVICE=C:\Windows\EMM386.EXE NOEMSrem ====================================================================rem = Locate and set up DOS =rem ====================================================================DOS=HIGHBREAK=ONSHELL=C:\Windows\COMMAND.COM /E:768 /pBuffers=10,0Files=60DOS=UMBLastDrive=ZFCBS=16,0Stacks=0,0rem ********************************************************************rem ** Set up devices **rem ********************************************************************rem ====================================================================rem = SCSI controller =rem = Under Windows 95/98 it is likely that you will not need to =rem = install a specific driver 16 bit for your SCSI controller. =rem = If available, you should use the Windows 95/98 drivers in =rem = preference as they will be (a) faster and (b) not consume =rem = valuable MS-DOS memory in the first 640K. =rem = =rem = However, if you do, the following gives an indication of its =rem = installation for a Magneto-Optical drive (Windows 95/98 =rem = provides proper 32bit replacements for the Adaptec drivers =rem = indicated). =rem ====================================================================rem DEVICEHIGH=C:\SYS\ADAPTEC\ASPI8DOS.SYS /Drem DEVICEHIGH=C:\SYS\ADAPTEC\ASPIDISK.SYS /D[Common]rem ====================================================================rem = Display card =rem = DigImage utilises standard ANSI control sequences for =rem = controlling screen format and colour at a Fortran level. =rem ====================================================================DEVICEHIGH=C:\Windows\Command\ANSI.SYSrem ====================================================================rem = Country specific information (UK) =rem ====================================================================Country=044,850,C:\WINDOWS\COMMAND\country.sys
AUTOEXEC.BAT for Windows 95:
@ECHO Offrem ********************************************************************rem ** AutoExec.BAT for Windows 95/98 **rem ** ****************************** **rem ** **rem ** This file contains a sample AUTOEXEC.BAT file for DigImage **rem ** when running under Windows 95/98. For operation under MS-DOS **rem ** and/or Windows 3.1x, please refer to Document\AutoExec.TXT. **rem ********************************************************************rem ====================================================================rem = Basic MS-DOS set up =rem ====================================================================VERIFY OFFPROMPT $P$GVERrem ********************************************************************rem ** Environment Variables **rem ********************************************************************rem ====================================================================rem = MS-DOS settings =rem ====================================================================set DIRCMD=/orem ====================================================================rem = DigImage pointers =rem = ----------------- =rem = DigImage =rem = This should point to the directory in which DigImage is =rem = installed. =rem = Video =rem = This should indicate the type of video recorder being =rem = controlled by DigImage. The supported options are: =rem = AG7330 Older Panasonic SVHS =rem = AG7350 Newer Panasonic SVHS =rem = BRS822 Expensive JVC SVHS =rem ====================================================================set DigImage=C:\Img\DigImageset Video=AG7350rem ====================================================================rem = Disk Driver pointers =rem = -------------------- =rem = On our systems these variables are used by standard batch =rem = files on a number of different machines with different =rem = configurations and drive assignments. They provide a standard =rem = way of accessing a particular device, or detecting if such a =rem = device is present. =rem = OptDisk =rem = Points to the Magneto-Optical disk drive. =rem = CDRom =rem = Points to the CDRom drive. =rem = NetDisk =rem = Points to a networked disk drive I always connect to (my =rem = Laptop) =rem = Server =rem = Points to the network file server (there will be one soon, I =rem = hope!). =rem ====================================================================set OptDisk=D:set CDRom=F:set NetDisk=G:set Server=Z:rem ====================================================================rem = Directory pointers =rem = ------------------ =rem = These environment variables are required by various pieces of =rem = software to locate specific files or directories. =rem = Lib =rem = Specifies where to search for language libraries. =rem = Tmp =rem = Directory for temporary files. Required by Microsoft languages =rem = (e.g. Fortran 77) and DigImage.rem = Temp =rem = Directory for temporary files. Required by Windows and various =rem = other applications. =rem ====================================================================set Lib=C:\Libset Tmp=C:\Tmpset Temp=C:\Tmprem ====================================================================rem = Computer and user name are useful for DOS Batch files =rem = "Moana" = Maori for "Sea". My laptop is called "Hauiti" = =rem = "Light breeze" and my desktop at home is "Maui" who was the =rem = god who caught the fish (the North Island) from the canoe (the =rem = South Island) and so created New Zealand. =rem ====================================================================set CompName=Moanaset UserName=Stuart Dalzielrem ====================================================================rem = Memory resident utilities and drivers =rem = ------------------------------------- =rem = DosKey =rem = Provides memory and editting functions at the DOS command =rem = prompt. =rem = KeyB =rem = Ensures the correct keyboard layout (101 key US, 102 key UK, =rem = etc.) is used. =rem ====================================================================LoadHigh C:\Windows\Command\DosKey.COM /insertLoadHigh C:\Windows\Command\Keyb uk,,C:\WINDOWS\COMMAND\keyboard.sysrem ====================================================================rem = Paths and path variables =rem = This will differ, depending on your precise machine setup. In =rem = my case many things are pointed to by batch files in C:\BATCH =rem = rather than included explicitly on the path. The DIGIMAGE\BIN =rem = directory need not be on the path if you are only using code =rem = linked with the dynamic overlay linker. If you are using the =rem = older static overlay technology, then DIGIMAGE\BIN must be =rem = on the path. (If DIGIMAGE\BIN is not on the path, then there =rem = must be batch or .PIF files somewhere on the path pointing to =rem = the appropriate executables.) =rem = =rem = Note that the original DOS directory is included on this path, =rem = even though we are running Windows 95/98. Normally this will =rem = not be required. =rem ====================================================================PATH C:\Batch;C:\Bin;%DigImage%\Bin;C:\DOSrem !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!rem !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!rem !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!rem ********************************************************************rem ** Other Settings **rem ** These are specific to my machines and will not be required **rem ** elsewhere, although you may have other stuff you want to put **rem ** here instead. If possible, try to avoid things that steal **rem ** memory permanently! **rem ********************************************************************rem ====================================================================rem = MultiEdit =rem = Set default mode =rem ====================================================================set ME_Line=/X132 /Y44set ME_Mode=51rem ====================================================================rem = GhostScript =rem ====================================================================Set GS_Lib=C:\Sys\Printer\GhostScr\GS3.51;C:\Sys\Printer\GhostScr\Fonts
The frame grabber card is mapped into the computer's memory space through a 512KByte window which must be located somewhere in the first 16MBytes of address space. With older computers this limited the amount of RAM to 8 or 12 MBytes as the frame grabber card will not function if RAM occupies the same address space as the frame grabber. However, with the newer "Plug and Play" machines, the BIOS often allows a "hole" to be created somewhere in the first 16MBytes of the address space, thus allowing the frame grabber to be used even if 16MBytes or more of memory are actually installed. The amount of useful memory may be less than that actually installed due to the existence of this hole. The method of setting up this hole depends on the machine's BIOS. In most cases the hole can be created from the BIOS setup utility. This is often accessible by pressing a particular key combination during bootup.
If you have 16MBytes or more RAM installed and you wish to run Windows (3.1x or 95/98), you may do so using a single configuration and avoid rebooting the PC when switching between Windows and DigImage. Simply choose the DigImage configuration from the example above which offers the required number of buffers. This will reserve some memory for exclusive use by DigImage, but still allow around 11MBytes for Windows in a 16MByte machine, or 27MBytes in a 32MByte machine.
At present DigImage supports a maximum of 32 buffers (16 in extended memory for the DT2861 or 32 for the DT2862). There is thus no point in reserving more than this for use exclusively by DigImage. Some of the additional memory left in the XMS pool will also be used as a cache for Dynamic Overlays, significantly increasing the speed of DigImage when compared with having to load the overlays from hard disk. Thus there are a number of advantages to having more than the minimum amount of memory required for DigImage.
Unfortunately not all BIOSes appear to handle the creation of the hole correctly. The end result of this incorrect handling appears to be that the memory above the 16MByte mark is not accessible. The following discussion assumes you have 32MBytes or more memory installed. With Windows 95/98 you can determine how much memory Windows thinks it has by looking at the System Properties properties sheet. This is accessed by right-clicking on "My Computer" then selecting "Properties". If everything is working correctly, Windows 95/98 will report more than 16MBytes of memory. The precise amount is difficult to estimate as it depends on the other cards installed and the system BIOS. In any event, it will probably be slightly less than the amount of installed memory less the amount reserved by the /INT15 switch and less the 1MByte hole.
If Windows 95/98 reports less than 16MBytes and you believe there should be more, either your BIOS is not handling the creation of the hole correctly, or Windows 95/98 is failing to compute the memory correctly. One way of checking to see if Windows 95/98 can access the memory above the hole is to reserve all the memory below the hole using the /INT15 switch. On our machines (Gateway 2000 Pentiums with AMI BIOSes), which handle the hole correctly, the following is observed after setting /INT15 and rebooting:
| Hole size | Switch setting | Behaviour | Comments |
| 1MByte | /INT15=13312 | Windows starts but hangs after "logon" prompt | Reserve 13MBytes. This leaves only the 640KByte base memory plus 1MByte extended memory. The machine appears to hang when trying to connect to our network. This is probably due to the network card requiring memory in the first 16MBytes (it is an ISA bus card) in order to function correctly, and 1MByte is not enough. It is possible that the display adapter may also require memory in the first 16MBytes. |
| 1MByte | /INT15=12288 | Windows starts correctly | Reserve 12MBytes. Windows functions normally. It reports the expected amount of memory relative to no /INT15 switch but with a hole in memory. |
| 1MByte | No /INT15 switch | Windows starts correctly | Windows reports 29MBytes of memory. |
| No hole | No /INT15 switch | Windows starts correctly | Windows reports 32MBytes of memory. |
On machines which do not handle the hole correctly, Windows reports that there is insufficient memory and does not boot correctly.
From version 2.0, DigImage has been able to run at a DOS prompt under Windows 3.1, 3.11 and 95/98 (but not NT 3.5, 3.51 or 4.0). To achieve this, DigImage requires in the vicinity of 570KBytes of RAM to run in at the DOS prompt. If there is insufficient memory avaiable, one of a variety of error messages may be generated, either on trying to start DigImage or at a later stage when DigImage is attempting to open a file. If there is insufficient memory, return to the optimisation phase in section 3.5 and attempt to free additional memory. There is generally no difficulty freeing up sufficient memory when running under Windows 95/98, but it can be problematic under Windows 3.1 especially when running a network adapter.
The four main components of DigImage - DIGIMAGE, TRK2DVEL, DIGIPLOT and DIGIFILE - are each supplied with Program Information Files (PIF) to inform Windows of their requirements. They are also supplied with a variety of icons which may be used to set them up as items in a Program Manager group (Windows 3.1x), or the Start Menu/Desktop (Windows 95/98). Installation of these is a purely manual process and should be undertaken in the normal manner. The icons and PIF files will be found in DIGIMAGE\BIN.
Most users, however, find it more convenient to start DigImage from a DOS prompt rather than double clicking on an icon. This may be done with the DOS prompt running either in a window or full screen.
Some users may wish to set up associations within File Manager/Explorer so as to start certain components of DigImage if a double-click is performed on a file name. Suggested associations are:
| File Extension | Application | Comments |
| .CMD | DIGIMAGE | Will start DigImage with the specified command file running. Note that the command file may be intended for Trk2DVel rather than DigImage! |
| .DIG | DIGIMAGE | Starts DigImage and leaves it in the main menu |
| .JNL | DIGIMAGE | Starts DigImage and attempts to run it as a command file. |
| .PLT | DIGIPLOT | Starts DigiPlot and displays the corresponding plot. |
| .IND | TRK2DVEL | Starts Trk2DVel and leaves it in the main menu |
| .PAR | TRK2DVEL | Starts Trk2DVel and leaves it in the main menu |
| .PRT | TRK2DVEL | Starts Trk2DVel and leaves it in the main menu |
| .GRD | TRK2DVEL | Starts Trk2DVel and leaves it in the main menu |
| .PIC | DIGIFILE | Starts DigiFile, converts the image file to PostScript and downloads it to the printer specified in CONFIGUR. |
| .DPS | DIGIFILE | Starts DigiFile, converts the .DPS file (a special form of PostScript lacking the normal header information) into a normal printable (.PS) PostScript file and downloads it to the printer specified in CONFIGUR. |
WARNING: Only one DigImage component may access the frame
grabber at any given instant. If you attempt to start DigImage
while there is already a component running, DigImage will only
allow it to start without frame grabber support.
DigImage documentation page
DigImage home page
Stuart Dalziel's home page