Copyright (C) 1986-2008 by Daniel H. Hudgins, All Rights Reserved.

No part of "This Web Site" (HTML document), including associated files, may be: distributed, sublicensed, transmitted, copied, archived, mirrored, modified, bundled, embedded, sold, given away, rented, loaned, or shared in any form without express written permission in a formal Vendor agreement contract dated and signed in ink obtained directly from Daniel H. Hudgins by registered postal mail. All agreements for permission to distribute expire after a period no greater than one year from the date of the signing of the agreement by Daniel H. Hudgins. See the current "EULA" for information regarding limited copying and storage for the purpose of "Beta Testing" "This Web Site."

To view or use the current version of this Web page you may need to reload or refresh the display of this page by your browser. Just clicking on the browser's [Reload] or [Refresh] icon may not be enough to insure that all of the page's most current contents have been cached and displayed. Some browsers may have additional commands to help display the page's most current contents such as: holding down the [Shift] key and clicking on the [Reload] icon, holding down the [Control] key and clicking on the [Refresh] icon, holding down the [Control] and [Shift] keys and clicking on the [Refresh] icon, pressing the [Control] and [F5] keys, pressing [Control] and the [R] key, or some other combination of keys or clicks. Check to see which commands your HTML browser uses to load the most current page contents into its cache and then to display them onto the screen.

This Web site is dedicated to the thousands of "users" of my programs, those who have helped test my programs over the last 22 or so years, and especially those who shared their experiences with me.

You must read this notice: This is a licensed Web site (HTML document and associated files). You must read and agree to be legally bound in contract by the Terms of Use and conditions given in the End User License Agreement ("EULA"), Legal Notices, Instructions, Warnings, Disclaimers, and all other text in "SECTION: 0" of "This Web Site" (HTML document and associated files) before reading or using any of the information, software programs, and or files, contained in, linked to, and or associated with, "This Web Site" (HTML document and associated files). Any use or "Beta Testing" of "This Web Site" constitutes your acknowledgment of your full agreement with the current End User License Agreement ("EULA") and your decision to have this current license supersede all prior and contemporaneous agreements and understandings. Information and files in "This Web Site" (HTML document and associated files) have been placed here so that long time users of "The Author's" programs DANCAD3D.COM (tm) , DANCAM.EXE (tm) , or DANPLOT.EXE (tm) could help proofread the text of the documentation files or screens displayed, and also help test data files, example files, and or any software programs that might be made available from time to time, to aid "The Author" in finding mistakes, bugs, and other errors, omissions, defects, mistakes, and faults. Everything in "This Web Site" (HTML document and associated files) is "Beta Test", "Beta Code", Experimental, Preliminary, requires proofreading, or is being evaluated for possible revision, and is NOT warranted to be free of defect. To help "The Author" report any bugs, foul-ups, defects, or mistakes that you find, see "SECTION: 8" for instructions. "This Web Site" (HTML document and associated files) and all other files and programs by Daniel H. Hudgins are made available "AS IS" without warranty of any kind express, expressed, or implied. All offers and specifications are subject to change or discontinuation without notice of any kind. Please read "SECTION: 8" of "This Web Site" (HTML document and associated files) before trying to contact "The Author."

Some of the text in this section was derived from the BULLETINS that were posted in the INDEX.HTM page. Since there were several Windows (tm) related issues I decided to make a special section for them for "Beta Testers" to review if they experience problems while running my programs under Windows (tm).

When Windows (tm) is mentioned in this Web site, what should usually be inferred is that Windows 95 OSR2 (tm) is the version being referred to, since there may be variations in how various versions allow DOS programs to operate or interfere with how DOS programs can operate.

In general my CAD programs have at times been able to be booted in a DOS window under Windows 95 OSR2 (tm) or Windows 98SE (tm), although some issues may exist that might cause perhaps serious problems when certain features are being used, particularly if you try to pop in and out of my programs to Windows (tm) while my programs are running. Windows 95 OSR2 may not be able to be used on new faster computers, so Windows 98SE (tm), Windows 3.11 (tm) or DOS may be needed for such systems. Versions of Windows (tm) newer than Windows 98SE (tm) may not be fully or in any way compatible with my programs or may require switching them into Windows 98SE (tm) compatibility mode.

My CAM programs may perform better when run directly under a DOS type OS and is some cases, or when some features are used, only give satisfactory operation when run exclusively under DOS, even though they might give sufficient operation under Windows 95 OSR2 or Windows 98SE for some non-critical applications when they are the only program running on the computer. FreeDOS (tm), a "free" DOS OS might be able to be used with CAM programs if you need to use a DOS type OS in place of some Windows (tm) version. In some cases it may be possible to make a "DOS" like boot disk using Windows (tm) by formatting a floppy disk with some Windows (tm) system files and then reboot your computer from that floppy disk to have "win-dos" load as only to a DOS prompt, so as to still be able to run my CAM programs off of your computer's harddisk (you would then take the floppy disk out and re-boot to go back to running the fill Windows (tm)).

Some of the information below is derived from several bulletins that were issued relating to Windows (tm) issues and other sources. Other issues may exist if you find any please report them. Please read all of the other documentation since it may provide additional information.

It has come to my attention that some Windows (tm) programs running in background can automatically force popping out of my programs running in a DOS window without your permission. This may be a serious problem since Windows (tm) may not be able to restore my programs to operation after it has forcibly popped you out of them at some random time, and may be particularly problematic while my programs are in SVGA graphics mode or doing some other tasks such as printing. This may be worse than the problem of bumping the "Windows (tm) Key", since you can use a keyboard that does not have that key. In this case you might have almost no control of when some background program might pop you out of my program, possibly causing a total loss of your work in the workspace. Programs such as: Modem control or Internet connection software, Download programs, CD-ROM burning or playing software, and similar programs might have the ability to force a program pop out in order to give you some kind of notice or for another reason. No program that can pop you out of my programs should be running on your computer at the same time as my programs. By pressing [Ctrl]+[Alt]+[Del] under Windows (tm) you may be able to disable trouble making programs running on your system one at a time, without disabling those programs that are needed and do no harm. Do not press [Ctrl]+[Alt]+[Del] while my programs are running, rather quit back to the DOS prompt, then press [Ctrl]+[Alt]+[Del].

You should not use one of the keyboards that have the "Windows (tm)" key on them that pops you out of a program, since if you bump that key accidentally you may not be able to get back into my program and you may lose all of your work in the workspace or lose open files. Rather, you should use an older "AT compatible" type keyboard that does not have the "Windows (tm)" keys on it. If your mother board as the small keyboard connector you should be able to get an adapter cable to convert from the older large keyboard connector to the smaller keyboard connector. I do not recommend using a USB keyboard with my programs at this point since DOS program operations predate USB keyboards. If the keyboard locks up after returning from a pop out to the Windows (tm) desktop or some other program, but the mouse still works, and you get trapped in the Draw part of the Drawing Editor you may be able to escape by pressing both mouse keys at the same time which the CAD program interprets as pressing the mouse center button on a three button mouse, since the center button on your three button mouse may not work under Windows (tm), or you just have a two button mouse, pressing both the right and left buttons may be the only way you can toggle the cursor control from the drawing cursor to the menu cursor, you may have to make several tries at clicking both mouse buttons at the same time since it is hard to do, once you get the menu cursor "turned on" roll to the [Q]uit option and left click the mouse button on that option, which should bring you back to the CAD programs Main Menu, then save your drawing elements with the Files Save Elements command (you may need to use or make an odd filename by scrolling up or down in the used filenames list that comes up when you roll the mouse up and down at a file prompt in the CAD programs) then quit the program and preserve the workspace, then shut down and reboot your computer to try to get the keyboard to work again.

It has come to my attention that some Windows (tm) type and possibly some other OS type file copying programs may change the file attributes of files to be used with my programs making those files unable to be opened or used. My programs may report various errors when trying to open or use such altered files since none of the file attributes should be set in files that my programs use. This problem may be able to be corrected by using the DOS command ATTRIB -R *.* or ATTRIB -S -H -R -A *.* in each sub- directory or folder that any files are in that my programs will access. You might use the Windows (tm) file properties option to check the attribute bits of the problem files, none of the attribute boxes should be checked, i.e. un-check Read only, Archive, System, and Hidden attributes. The DOS command ATTRIB can also be used to view the file's current attributes, e.g. ATTRIB FILENAME.EXT, see your DOS program manual for more information about the ATTRIB command. If many files are affected, it may be easier to try using the DOS command ATTRIB -R *.* or ATTRIB -S -H -R -A *.* in each sub-directory rather than un-checking the attributes for each file with the Windows (tm) command. This problem may occur if you copy files to a CD-ROM in order to transfer them to another computer, when the file is copied off of the CD-ROM the new file copy may not open because the attribute bytes were set when the file was recorded on the CD-ROM or copied from the CD-ROM. This problem may also occur when unzipping files from a downloaded ZIP file, or if you zip files to save disk space, so always un-zip the files in such a way that none of the file attribute properties are set in the un-zipped files. Since some file copying programs may change the file attributes "willy- nilly" you may not know that the attributes have been changed without your permission. Once you know that this problem can occur, you should be able to try to fix it so as to restore the files to normal status. Be sure that you do not alter the file attributes of any files that require their file attributes to be set, e.g. system files and such. Do not run INSTALL.BAT in a directory or sub- directory where files need their attributes set, since INSTALL.BAT may alter or remove the file attributes of all files in that directory. My programs and files being worked on with or used by my programs should be in their own separate sub-directory and not a sub-directory used by other programs or another program.

It has come to my attention that if you have a Windows (tm) printer driver installed that captures the printer output before it gets to the printer port, and you are using another, i.e. different, printer, plotter, or possibly a CAM machine on that printer port, the Windows (tm) printer driver may insert incorrect characters, delete characters, or otherwise alter the data stream to the printer port possibly causing what might be some serious problems. A Windows (tm) or other print spooler may also cause similar problems. Be sure to disable any Windows (tm) printer drivers or any spoolers you may have installed before using the printer ports for or with some other device than the one the driver installed supports. You may be able to install another printer port card into your computer's slot and instruct or configure the Windows (tm) printer drivers not to intercept data to that port, so that you have a printer port that is free of meddling for use with other devices.

It has come to my attention, by way of published sources other than by way of my personal experience, that a problem in Windows 95 (tm)'s and Windows 98 (tm)'s file called "Ndis.vxd" may produce a "divide by zero" error when you try to run them on a computer with a CPU speed of 2.2GHz or faster. A fix may be available for Windows 98 (tm), but not for Windows 95 (tm), effectively limiting the maximum CPU speed you can use with Windows 95 (tm) to 2.1GHz when "Ndis.vxd" is involved. It is unclear as to the frequency with which "Ndis.vxd" is active, i.e. just on initial installation, every time new hardware is installed, when the CPU or CPU speed is changed, or every time the OS is booted. You may need to investigate how this problem with "Ndis.vxd" might impact your particular system. Please see also additional discussion of this issue in SECTION: 2's FAQ. If you are planning on upgrading your CPU, and are using Windows 95 (tm), you should probably be careful about not selecting a CPU that is too fast for the system to operate. Processors made by AMD (tm) may cause the "Ndis.vxd" problem at clock speeds less than 2.1GHz because some of the AMD (tm) processors may produce the equivalent throughput of some INTEL (tm) processors of a higher clock speed, e.g. a real clock speed of 1.9GHz on one type of processor may act like 2.2GHz in another, so the CPU clock speed may not be enough to tell if you will experience the "Ndis.vxd" problem. Windows 98SE (tm), or maybe later editions thereof, do not seem to suffer from the "Ndis.vxd" problem, but may need to be patched for use with new larger harddisk sizes.

If some program features that use the Port I/O do not seem to be working check that you are using an OS or OS settings that will allow for direct Port I/O. See SECTION: 2's FAQ for more information. Some newer versions of Windows (tm) may interfere with direct Port I/O, although there may be some work arounds such as using Windows 98SE compatibility mode.

Although not exclusively a Windows (tm) issue many users may be using a Windows (tm) browser, so, if you have noticed that some of the image files in this Web site that have a pixel resolution larger than your screen size are displayed only within the boundaries of your screen at degraded resolution you may need to use a different browser while viewing this Web site, or alter your browser settings to disable this "shrink-to-fit" feature. See SECTION: 2's FAQ for more information.