Tips for running Open Access under Windows 95

by Michael Paine

In association with the Australian Open Access User Group

Are you running Open Access or other DOS programs under Windows 95/98? Tell us your tips and tricks so we can pass them on.

There is also a page with unflattering comments about Windows 95 operating system.

[WIN95 Configuration] [Printing from DOS applications] [Printing on WIN98 Networks] [OA Slow to Load] [Windows NT/XP] {Xtree tips] [Hyperlinks] [Networks - see also Printing] [Replacing hard disks] [Tips for Hard Disk (System) Backup] [Downloads and help]

---

WIN95 Configuration Tips

_{There are many other WIN95 tips at Windows 95 Annoyances}

Displaying file extensions in search/explore windows

The default installation of WIN95 display pretty, but meaningless icons instead of file extensions when you "explore" or the "Open" window is accessed. To display the full DOS filename (eg readme.txt instead of [icon]readme) click on MY COMPUTER, select View/Options/View and deselect the item "Hide MS-DOS file extensions for file types that are registered". (Tip from Keith O'Donnell).

Selecting files for action

When selecting multiple files from a list by clicking with the mouse hold down the Shift key to select a range of files or hold down the Ctrl key to select several, non-consecutive individual files.(Tip from Keith O'Donnell).

Passing parameters when starting a DOS application

When starting a DOS application such as Open Access in WIN95 you can pass a user-defined parameter by adding a ? after the command line. With the mouse over the icon concerned click the right mouse button and select Properties. Now select Program. In the "Cmd line" field add a space then a question mark after the DOS command line.

See Keith O'Donnell's tips about starting OA with a chosen configuration.

The trick also works with programs like Xtgold, where the parameter is the path that Xtgold logs to. See Xtree tips.
 

Printing mutiple pages

Several users have reported problems printing multiple pages. Microsoft's Knowledgebase might have the answers. I did a quick search and found these references. One tip from Microsoft was mentioned in the Newletter in 1996: for printing from Windows 3.x try printing to LPT1.DOS (a setting in the Windows Control Panel). See also Jack Huff's tips below.

---

Jack Huff from the USA has sent in some very useful tips:

Subject: OA4 Printing on WIN95 Network Date: Mon, 11Aug 1997 11:56:52 -0700 From: Jack Huff

I don't have all the answers regarding printing problems on a Windows 95 network, but here is some information.

PRINTER SETTINGS

Click on START at the Desktop, then select Settings, then printers. Select the existing printer you are using, then click on File. Select Properties. Test the settings in the following areas to look for solutions to problems.

Details/Port Settings Details Spool Settings Fonts

PRINTER PORT PROBLEMS

The printer may be plugged into a different port than you are attempting to use. On a network the port may be captured, or you might have to use the network print spooler. Click on Start, then Settings, then Control Panel. Double click on the System icon. Choose the Device Manager tab. Find the printer port and click on properties. On the General page, Device Status area. see if the port has a problem. If it does you may have to contact the printer manufacturer or the computer manufacturer.

PRINT JOBS ARE NOT COMPLETED

Check the Printer Memory Tracking in the Device Options page of the printer's properties sheet. The printer may be short of sufficient memory.

THE PRINTER DOES NOT WORK AT ALL STATIONS ON WIN95 NETWORK

At the computer to which the printer is connected, choose the Share the Printer with the Network Users at the Network dialog box (File and Printer Sharing). You can also go through the sharing page of the printer's properties sheet.

SWITCH BOX

If you are using a print sharing device or switch box, bypass it and plug the printer directly into the computer to see if the printer works properly. If it does, the problem is in the print sharing device or switch box.

Some of this information I obtained from "Windows 95 Installation and Configuration Handbook" published by Que.

Cordially, Jack 

---

Subject: WIN95 Hints Date: Tue, 09 Dec 1997 15:29:53-0500
From: Jack Huff 
Organization: Huff Communications Inc.

Should you not yet be aware of it, Tom Solarek passed away suddenly and unexpectedly recently. He was the author of the WindowBase book on the DASL script language.

Here are a few WIN95 tips that may not have come to the attention of your users:

• At the Control Panel/Printers/Details/Spool Setup, uncheck everything except Print Directly to Printer.
• Early versions of Windows 95 may be incompatible with the DOS extender in OA4, causing database queries to malfunction. To prevent OA4 from trying to use expanded memory, which in turn triggers usage of the DOS extender, there should be no expanded memory in your RAM. This can be accomplished by the line
device=emm386.exe noems
in your CONFIG.SYS file if one is used in your computer system. The parameter NOEMS means no expanded memory. Since other problems may also be caused by early versions of WIN95, you should upgrade to a recent version.
• A blank screen when starting OA4 can be caused by a wrong screen saver setting in WIN95. At the Control Panel/Display/Screen Saver, SHUT OFF MONITOR may be checked. It should not be checked.
• In Windows 3.1 the printer setup must be active on the computer to which the printer is connected (if on network) but it doesn't matter how the printer is set up.
• If print jobs do not start promptly in Windows 3.1 or Windows 95, there may be insufficient RAM in the printer or insufficient RAM allocated by Windows. Another cause for the same problem in Windows 3.1 can be fixed by disabling the print manager.
• In Windows for Workgroups/Windows 95 network, an error message starting with "Put code disk...." may occur if the OA4 file APP.SPI in the OA4 directory is not shared. Make sure that all files used by SM-Plus are shareable.


Cordially, Jack Huff


---

Printing on Windows 98 Networks

From Steve Hayes, SPIRAL COMPUTERS  13 April 2001. Steve@spiral.co.uk

I noticed that there was concern over printing in Open Access under WINDOWS 98.  The solution is to add the following lines to SYSTEM.INI in the WINDOWS directory:

After [386]Enh block put extra lines:

[Network]
PrintBufTime=10

[IFSMGR]
PrintBufTime=10

Also, always run an OA application from an icon and set up the Memory under PROPERTIES to have EMS NONE.  We have found this cures nearly all print problems and even works with WINDOWS only printers with a DOS window – not recommended however.

We continue to maintain and support our Customer Base of Open Access Users, all with compiled
versions, so are looking forward to the DSPI announcement – please advise any other news or contacts.
 

---

Subject: Loading Open Access from Windows

Apparently OA searches RAM when loading. This can take minutes if you have a large RAM. To instantly load OA try pressing Pause then Esc! (tip from Frank Doevendans, DISPI bv)


---


From: "Graeme Vines"  Tue, 9 Dec 1997
I would like to pass on another comment about loading OA4 under Win95:
• 1. Have a shortcut to OA4 on your desktop.
• 2. Double click on the shortcut icon.
• 3. Press Alt-Enter once and OA4 opens up 'instantly' in a small window.
• 4. Click on the expand window icon on the tool bar of the window (that is the icon showing 4 arrows) and bingo you have full screen loaded.

 

 
 
 
 
 
 
 

I have timed this procedure and it takes 5 seconds (occasionally 6 seconds) to fully load OA4 ready to use.

Regards, Graeme Vines.
 

Top of page


---

Subject: OA4 under NT4/Intranetware
Date: Sun, 8 Mar 1998 15:02:55 +0000

Our old system was a DOS/Netware 2.2 network. We didn't know whether to run Intranetware or NT4 Server on our new file server. Several consultants told us it was a toss up which one was better, but the consensus was that Intranetware (which is Netware 4.12 in disguise) was better established, probably more stable, and cheaper, so that's the way we went, and we now have an all-Pentium five terminal NT4/ Inranetware system running OA4 on all terminals. OA4 queries suddenly run a lot faster ! .

Once you have OA4 running under NT4 it looks exactly like OA4 under DOS. The advantage is that you can run OA4 simultaneously with other programs, and flick backwards and forwards from one program to the other by pressing Alt-Tab. For instance we run a reference CD-ROM on our file server which any user can refer to, at the same time as they are running OA4. They can also run multiple copies of OA4 simultaneously.

Getting OA4 running in the first place is another kettle of fish. If you aren't an NT4 / Intranetware expert then get a good consultant to install it, one who already has experience in running DOS applications under NT4/Intranetware. You have to use a suite of utilities called Netuser which are very poorly documented, but the consultants have access to a lot of extra documentation from their own website.

We were lucky in finding a consultant who also knew OA4. He hooked our new file server to the old one and then used a utility called Migrate to copy all our software over to the new server. OA4 then came up on the new network as if nothing had happened ! I was most impressed. It only took a couple of hours. The only problems occurred when we tried to print, either no printing happened or it was very slow, but a bit more fiddling fixed up all that. For Sydney users, our consultant was George Nade of Business Computer Sevices, Ph (02) 9683 4068. Recommended. He supplied all the hardware and installed the system.

The next step will be to enable any terminal to send fax's and email, which are standard faclities of Intranetware, and then to enable web browsing from some terminals, which we will use to look at our suppliers' web sites.

Regards

Michael White
Hotline Books
hotbooks@acay.com.au
Home page http://www.hotline.com.au


---

OpenAccess in a Novell Network and WinXP Workstations

If a Client Worksstation runs with WinXP in a Netware Enviroment you have to install the OA
Netbios Version on that Novellserver and remove the Novell Version of OA from there. The OA
Netbiosfiles must include the OA4.SPI, the APP.SPI and the *.lib files. After doing that OA
runs fine in that NovellNetwork using DOS, WIN9x, WinNT and WinXP Clients. Dont forget to run
the Netbios.exe on DOS Clients.
 
Alfred Unkrig - Oct 02

---

Xtree & WIN95/98

by Michael Paine, December 1998

Good ol' Xtree works fine under Windows 95/98 but there are a few things to remember for making the  most of it.

Memory limitations

Xtree was never intended for use with 2Gb hard disks - particularly the number of directories and files that are now typical on a PC (to cope with all those useless features you never really wanted). Almost certainly if you try to run Xtree without modification you will strike an "out of memory" error message and only part of the disk will be logged. This can be overcome by configuring Xtree to only log to the root directory or, more useful, to log to a specific directory. The latter can be achieved by the following batch file:
[c:\xt.bat]
echo off
echo Loading Xtree
c:\xtgold\xtgold %1
[assumes xtree is in the xtgold directory]
From DOS just type xt c:\temp, for example, and Xtree will load and only log to the "temp" directory on the c: drive.
To do this from a WIN95 "shortcut" (PIF file) edit the shortcut properties [right click when the mouse is over the Xtree icon] to make the "cmd line" entry read:
c:\xt.bat ?  [note the space then question mark]. This prompts you for data (the path) when you double click on the icon.

Logging a branch

Once you have partially logged to a disk you probably want to log the entire branch of that directory. With the cursor on the directory of interest just press the "*" key (this could be the most useful key of all - don't forget it!). If you only want to log to one directory press the "+" key. To unlog (compact the display and hopefully save memory) press "-".

Long filenames

Sorry, but Xtree won't let you create or rename long filenames. It will, however, let you browse through all directories and copy to and from directories with long file names. In any case, for crash recovery purposes, I prefer not to use long filenames for directories (did you know that the DOS on which WIN95 is based cannot deal with them!). Unfortunately, many WIN95 installation programs create such directories and don't allow a choice. Similarly many installation programs create yet another new directory under the root directory rather than allowing the user to choose a sub-directory. The same thing seems to happen with program icons but at least they can be dragged to more appropriate directories after the installation has been completed [right click on the Start button and select Open to start this process].

History

Just about every action in Xtree which requires you to type in data (such as a filename or path) has a history list associated with it. Just press the "up" arrow to display a list of the last dozen or so items used for that command. This is an extremely efficient way to deal with repetetive copying.

Once you get used to these tricks Xtree is still one of the most useful file management tools around - it has features that are still not found in most of the flashy Windows file managers.

Links for Xtree Fans:

• Tips and tricks for using Xtree Gold from an Xtree fan club
• Calypso is a 32bit (read WIN95) file manager with an Xtree "feel"
• Ztree is a great 32bit file manager that is very similar to Xtree but without the memory limitations.
Top of page


---

Hyperlinks in MS Access

I have been experimenting with hyperlinks within MS Access. These allow you to automatically jump to a WWW address or other Windows applications  by clicking on a field or control with Access.
There are several tricks.
Firstly, you can set a field to be datatype Hyperlink. In this case when you click (once) on the field in a form the web browser is loaded and the page is opened. To edit the field (say to change the address) you
must right-click. This is a nuisance - I don't know why MS didn't allow program control.
Also I discovered that changing a field's data type from text to hyperlink can corrupt existing data.
On balance I recommend not using field datatype HYPERLINK.

Instead try the FollowHyperlink method. For example you could attach the following code to the On Double Click property of a field (in my case called HTTP) on a form:
On Error GoTo Err_hyper
 xs = "http://" & [HTTP]
 If MsgBox("Load HTML page: " & xs & " ?", 1, "           Web Browser Confirmation          ") = 1 Then
        Application.FollowHyperlink xs, , True
 End If
Exit_hyper:
    Exit Sub

Err_hyper:
    MsgBox Err & ": " & Err.description
    Resume Exit_hyper

When the user double clicks on the field containing the WWW address the web browser starts and links to the specified page.

You can also open HTML pages on the local PC but you must use the prefix "file://"  (eg file://c:\temp\junk.htm ). As usual it took me ages to find this out. Eventually I found the tip on a German MS
page:
http://aquarius.franken.de/docs/develop/VisualBasic/VBAGuide/015.htm#PG015C3

You can also launch other Windows programs such as Word. In this case the FollowHyperlink method looks for the DOC suffix (or others set up in your Windows configuration such as JPG and BMP). You should not have the "file://" prefix in this case (it will cause the file to be opened in a web browser).

Finally, the Hyperlinks functions are also available within Word and Excel (see the above web page for tips)

Hope this is of help.
Michael Paine


---

WIN95 Network tips

• East Carolina Uni: You can share folders on a network without making them visible to others by adding a dollar sign ($) to the end of the folder  name. Just tell those you’d like to share them with the names of the folders, and they can type them in.
• (MP) After transferring the WIN95 system to a new hard drive my PC didn't appear in the Network Neighborhood window - but others did. The network setup was correct, with drives and printers checked for sharing. I tried testing the Network card (shell to DOS and try NET DIAG on two PCs in the network to test the connections and protocol). Some things I tried were:
• The workgroup name might be case sensitive - check the use of upper and lower case on another PC
• Try using a different login name on the upgraded PC
• Uninstall the Adapter Driver (Control Panel/Network - click on the network adapter then REMOVE). Reboot the system and try reinstalling the Adapter.
• If this fails, uninstall it again then install another adapter (any should do). Then uninstall the false adapter and reinstall the proper adapter - this seemed to work for me!
• If this fails try physically replacing the network adapter (even though it works correctly WIN95 might no longer talk to it so replacing it for $50 might be less hassle)
• See also Microsoft support article  Q192534:"Troubleshooting Windows 95/98 Network Connection Problems".
• Lindy Myers: I finally solved the printer problem with the 95 network.

Situation.
2 computers networked with 2nd computer connected to shared printer.
1st computer has OA4 loaded and all stations.
2nd computer points to 1st for use of OA4 and data.
1st computer can print from network printer without a problem, set to LPTx or 2 in this case.
2nd computer would only print from attached local printer that is networked when lpt on printer
configuration is set to lptx.
The printing mostly would not work when the printer was set to LPT1.
This is tedious as the user has to set the printer to 1 each time they want to print, however
it works.
• The HP Officejet series (eg model 635) do not come with network support. The fax and scanning capabilities are only available from the PC to which the Officejet is attached. To use it as a network printer you will need to trick your network PC into thinking it is talking to a HP 550C Deskjet. See http://www.officejetsupport.com/oj600/faq/bpu01766.htm for tips.

---

Replacing hard disks

• Moving Windows95 to another drive - explains how to transfer entire contents from the old hard disk to the new one then make the new one bootable.
• (MP) Norton's Ghost (available with Norton System Works Pro) can make a copy of each hard drive or partitions on a  drive. The resulting image file could be copied onto a writable CD or kept on a secondary drive. Ghost runs from DOS so the steps to set up the new system might be:
• use Ghost to create an image file of your C drive.
• Copy the Ghostpe.exe file to a diskette.
• Create a "start up" diskette (Control Panel/Add_Remove Programs/Start_up_disk!) This should have the  DOS system and some utility programs such as FDISK and FORMAT. If the image file is on a CD ROM you will also need to active the CD drivers from CONFIG.SYS (e.g. DEVICE=AOATAPI.SYS /D:IDECD000)  and AUTOEXEC.BAT (e.g. MSCDEX.EXE /D:IDECD000 - note that the driver and MSCDEX.EXE will also need to be on the diskette - check your CD drive for its software needs). Use Notepad or similar to edit the files on the diskette.
• replace the old C drive
• boot from the "startup" diskette
• run FDISK to partition the new hard disk (for running Open Access and other non-32 bit program it is probably best to use 16 bit FAT and partitions no larger than 2 Gb (2047 bytes). In any case, the FAT probably needs to be the same as the old drive for Ghost to work.
• Make the new drive the active partition
• From DOS FORMAT the C: drive (does not need to have system files at this stage)
• From the diskette run Ghost and transfer the image file contents to the C: drive
• Your new hard disk should now be bootable to WIN95, since Ghost copied the system files and all WIN95 files to the new drive - try it (fingers crossed)!
• You can also use FDISK to set up an extended partition and to create "logical drives" in the extended partition - again consider limiting each logical drive to 2 Gb (you have no choice if you selected 16 bit FAT). You will need to FORMAT each new logical drive in order to use it.
• Once the system is working consider running Norton Systemworks to check the hardware and software for errors and optimise the running of WIN95.
• For some reason (maybe security features in WIN95) I had difficulty restoring the Network Neighborhood - see Networks.

Tips for Hard Disk (System) Backup

by Michael Paine  3 June 2000

Apparently the Windows operating system gradually accumulates errors that slow the system down and can cause crashes. Many corporations reinstall Windows every year, or more frequently, to overcome this problem.
These tips are for setting up a computer system in a way that can be easily "backed up" and "restored" to its original configuration. See also the tips on hard disk replacement

Software for Backing Up

There are numerous software packages around to backup important and changing data. These might not be suitable for a system backup. The idea is to create a package that can restore a system to its initial settings and configurations. To do this you will need specialised software such as Symantec's Ghost (Ghost Personal Edition is supplied with Norton Systemworks Pro). Ghost make a complete 'image' of a hard disk or partition on a hard disk. The software runs from DOS (even the A drive) so it can restore an image to the C drive or other hard disk drive, or to a new PC or hard disk.

Using Ghost to Make an Image of the C Drive

Once you have the PC set up properly, with all important software installed and configured then you can run Ghost.
• First make a bootable floppy disk that includes loading CD drivers. If there is room, include a copy of Ghostpe.exe on the floppy, or add it to another floppy.
• Boot the PC from the floppy disk. It should end up at the A> prompt.
• Type ghostpe <enter>
• From the menu selections, using the arrow and tab keys, choose     Local /  Partition /  To Image /
• Select the physical hard disk ("drive") containing the partition (virtual drive c:, d: etc) to be copied with the arrow key then press <enter>
• Using the arrow and tab keys, select the partition to be copied
• Using the arrow and tab key select the destination for the image file. This should have at least 50% of the disk space in use on the source drive. Type a file name for the image file and select OK
• Select High compression, OK OK
When the image making process ends copy the resulting *.GHO file to a CD ROM. Include the Ghostpe.exe on the CD, just in case.

Notes about Ghost

The terminology may be confusing. With Ghost a "drive" is a physical hard disk that may have more than one partition. A "partition" is a virtual drive on a hard disk. These you know of as C: drive, D: drive and so on.
Ghost gives you the option of using a compressed format that takes up about half the space of the original disk. The resulting 'image' file can then be saved on a CD ROM provided that it is under about 620Mb in size (CDs store about 650Mb) . Therefore for efficient use of the procedure the data on the partition being saved should not exceed about 1200Mb.
Ghost does allow you to "span" image files and these could be saved on multiple CDs but first you have to have the space on a hard disk to create the image files. Ghostpe also allows you to create an image file on another  PC using laplink style parallel port cables.

My tips are therefore:

• Use 2 Gb partitions on large disk drives
• Limit the used bytes on any crucial partition (particularly c:) to no more than 1.2Gb. This allows the resulting image file to fit on one CD. It also means you have enough space on that partition to create a temporary  image file from another partition, should the need arise.
• Keep a separate, regular backup of data files.
• Keep a record of any extra software installations made after the image file is created. You will need to reinstall these if you restore the system from the image file. It might even be wise to restore an image file before installing new software so that accumulated errors are eliminated. Then make a new image file of the latest configuration.
• Make CD backup copies of the installation disks for those old DOS and WIN3.1 programs that you still use. DOS programs can be simply restored to WIN95+ but old WIN3.1 programs like AmiPro need to be reinstalled if they are not on the image file..
• When you are first setting up a PC it may be  a good idea to create a fresh ghost image after a major installation and configuration. In this way a dud installation can be overcome (Windows remembers dud installations and seems to interfere with further attempts to install the software).

Bootable floppy disk

Test your bootable floppy disk to ensure that the CD drivers load. CONFIG.SYS and AUTOEXEC.BAT files will be needed for this:
CONFIG.SYS should have a line like
 DEVICE=AOATAPI.SYS /D:IDECD000
AUTOEXEC.BAT should have a line like
 MSCDEX.EXE /D:IDECD000
Also the driver file (in this case AOATAPI.SYS) and MSCDEX.EXE must be on the floppy disk

Restoring the system

Always make regular backups of important data. If you decide to reinstall Windows then, before doing so, check that your data backups are up-to-date and actually work! Next:
• Boot the PC using the floppy disk containing the Ghost program.
• Place the CD with the image file in the CD drawer. The CD drivers should have loaded so you can try listing the files on the CD with DIR E: (assuming E: is the drive letter). The *.GHO file should be listed.
• Type Ghostpe  <enter> (remember how to execute a DOS command!)
• GhostPE should load
• Choose LOCAL / PARTITION / FROM IMAGE
• Select the GHO file from the CD
• Select the drive (hard disk) and partition to restore to
Ghost will overwrite all files on the selected partition so be very careful the choose the correct settings.
Remove the floppy disk and reboot the PC. It should boot to exactly to same configuration as the one when the image file was created.
These procedures also work for a new PC or a new hard drive.
 

Update: April 2001: MANAGING PARTITIONS

Last year we discussed using Norton's Ghost to make a backup of the hard disk with all software installed and configured. This enables the system to be completely restored after an (all too frequent) operating system crash.
Ghost can compress a hard disk partition (say the c: drive) into one file. If this is less than about 630Mb then it can be saved on a CD and the system restored from a CD. Unfortunately most new computers come configured with one huge partition of several Gb. This makes backup and restoring procedures much more complicated.
DOS, Windows and even Norton's Systemworks do not have a utility for changing the size of partitions or adding new partitions (say a d: drive). There is software to do the trick: Partition Manager (http://www.paragon-gmbh.com/n_pm_descrip.htm)
The website has a limited function trial copy but you will need to purchase the full copy to be able to divide up a large c: drive.
Better still, get your computer dealer to create the partitions when the PC is first set up!

Update: May 2003: DFSee disk management software

Try DFSee for many of GHost functions plus a lot more tools for data recovery.

---


Subject: WIN95_tips - Backing up of OA files
   Date: Wed, 14 Mar 2001 21:36:17 +1100
   From: "Peter Freeman" <pfreeman@blueprintsecurity.com.au>
     To:  <mpaine@tpgi.com.au>
This is not so much of a WIN95 tip - my best tip for windows is to bypass it with a dos box as soon as you can get to one.

However this method of backing up of OA files and the like is what I would like to share:

1. Use an archiver such as LHA, PKZIP, ARJ.
    These hints work for ALL known archivers with only the slightest variation in  syntax. I use LHA not because it is better than PKZIP but only because I like the fact the same EXE performs both the compression and expansion functions.

2. To back up, and compress an entire structure you can use a one line batch file of the sort:  LHA U W:\OABACKUP\OABAK.LZH
C:\OA3  *.*  /X1 /R1

Analysed, this does the following:
    LHA                The name of the archiver LHA.EXE
    U                    Update option or command. Update adds a file to the archive if it does not already exist in the archive, updates the archive with a newer version of the file if the source file is newer than an already archived version of the same file.

    W:\OABACKUP is the pathname of the archive file to be created or updated

    OA3BAK.LZH  is the name of the archive file - the extension is optional. LHA will add it

    C:\OA3   is the source pathname (where the files to be backed up are to be found)

    *.*         the usual - select all files in the c:\oa3 directory

now to get fancy.....

    /X1    Store the archived files WITH THEIR ORIGINAL SOURCE PATHNAMES. ie store the full pathname for easiest and automatic restore into the same directory structure.

    /R1   Recurse into all sub directories below the C:\OA3 directory
 

Result:  A one line batchfile to backup and compress (typically by 60%) your data.

If you think OA users might be interested I can supply a full article written a few years ago with additional backup and compression techniques such as a 3 line batch to find all .BAT  or   *.?MK  and *.?F files anywhere on the system, and store their names in a control file, which is then passed to the archiver for backup, along with a PD utility that renames the backup to a format 010314.OA for grandfathering in date / name order for a file created on 14th March 2001.

Regards,
Peter Freeman


---


 
 

Prepared by Michael Paine (email) (home page). Last update 27 December 1998