IFILE/CFILE/VISION+ is a very simple system from a "technical" standpoint and it's requirements are modest - however - more and more - the requirements to keep ANY computer(s) functioning properly are becoming very very complicated. And that's simply because the hardware AND Windows are becoming more and more sophisticated; therefore, these products often require detailed technical knowledge and support to make them work properly. With that in mind we offer the following thoughts. We ask you to read this entire document; especially the last section In General: IFILE/CFILE/VISION+ is a full 32 bit windows based piece of software written using the Clarion/TopSpeed/SoftVelocity relational database manager. It does not have any hidden tricks and it does not use the registry. It’s simple to setup on any network and the manual contains instructions on how to do this as well a sample print-screen of what the shortcut should look like. Networking, Network cards and Cabling: - Ideally they should all be the same speed. - The drivers MUST all be matched to the current version of Windows you are running. Do NOT reply upon Windows to supply the "proper" driver; it's a really, really good idea to download the proper driver from the manufacturer's web site. - I know it sounds crazy - but - most network persons agree that the cables must not be bent or laid near a florescent light - If you’re using a wireless network make sure the security is turned on - Make sure your network is fast enough - perhaps a switch is required versus a hub/router. - Do NOT mix network protocols - you should only be using TCP/IP and for sure don't mix IPX and NETBEUI - Windows has a troublesome "feature" that is implemented for some Network cards - if the workstation is inactive for a period of time - Windows will put the network card to sleep - this "feature" must be disabled. This can cause a connection with a remote host to be lost with unpredictable results to applications running from that host. Windows 7 and later does this as a default so it should be disabled. - If your PC has a built-in network card (on the mother board) and another network card installed - you likely have a problem!!! - Maybe you should downgrade all PCs and Server to 10 mega bits per second transmission speed, then if the network is stable increase to 100 mbps and re-evaluate. - your hub/switch/router and the internet modem and your server MUST be on a UPS - most techs seem to agree that you should not mix versions of Windows - most techs will tell you - off the record! - that a wireless network is often flakey - our software is quite small in size and requires very little network speed, thus, if on your network you have some computers that can find a particular patient for example noticeably faster than another workstation; your network is likely malfunctioning - it seems that for Vista, Windows 7 and later the windows sharing centre prefers the \SAM folder to be in the \PUBLIC folder Video Cards: - Make sure the driver matches the monitor; download from the manufacture's site the proper driver for the monitor. - Make sure the Video Card is fast enough for the version of Windows you are running - and that it supports the appropriate screen resolution. For example, IF you were to upgrade an "older" computer (say 2-3 years) you may easily have a problem with the Video Card. Of course this is really important if you are using a 64bit version of Windows The Hardware and Environment: - we hear rumors that the Samsung CLP-620ND printer can cause problems with some versions of Windows. - You must have a UPS for the server. - you must have a UPS for the switch/hub/router and internet modem - You're hardware person might suggest a UPS on ALL computers - Check that the Power Supply on ALL machines is working properly. - MOST hardware failures begin with a bad power supply. For example, if you have a noisy fan or it doesn't work! you have a problem. - Static Electricity is often a big problem. If you get "shocks" - you have a problem. Make sure NONE of the computers are on the floor put them all on a couple of pieces of 2x4's. - If you have a carpeted office be suspicious. - The SDRAM or main memory of the PCs must be of the rated approved type recommended by the manufacturer. - Be sure that all computers are running at their advertised clock speed. This is easy to check by simply right-clicking on "My Computer" and checking the properties. - Make sure that there is NOT a more recent BIOS update file for the PCs. Unfortunately in XP some BIOS versions do not address the dual CPU status that Windows XP defines some motherboards as having. Interestingly enough Windows XP Professional sometimes reports that a computer has a dual CPU configuration when it does NOT! - Hibernation mode setting should never be used!!! - If a monitor is set up using a generic device driver and not the specific driver for that monitor, this can sometimes cause a situation where an LCD monitor is "overdriven" with its refresh rate. The correct monitor drivers should be set up on all PCs with LCD monitors. - It never hurts to check for a virus. - If you have a computer that freezes - then there is something broken on that computer.... - in a similar manner, if you need to Ctrl-Alt-delete, then there is something broken on that computer. Windows: - it works well under any Windows 64bit operating system… BUT!!! we find that often folks do not have a powerful enough computer for the 64bits. If find the computer is behaving strangely…. Meaning it freezes etc. something is broken - still on this same subject, we have had some techs tell us that if you have a mixture of computers on a network - some with 32bit Windows and some with 64bit it's best to run the software in compatibility mode if you find the computer is behaving strangely…. Meaning it freezes etc. - most technicians agree that you need at least 2MB memory for Windows 32bit and way more for 64bit… some say as much as 8MB - turn off write caching - in fact, turn off EVERY instance of caching you can find... NOTE: Most versions of Windows have more than one cache; there is often a cache for the hard drive and it's driver as well as the traditional Windows caching capability. - in fact, turn off anything that will suspend anything on ANY computer on the network... this is a really import, but subtle point - here's somethings that can easily cause you problems: MSN, a memory-resident FAXing capability, LogMeIn being active all the time, scanning software being memory-resident all the time - Also Microsoft’s Security Essentials is a known DataBase killer, so it must not be used… if you are using it then to remove it you need to do three things: 1) Remove it using the Windows removal tool 2) Delete the actual folder 3) Run a registry cleaner - Our software requires full access rights on each workstation and the server; perhaps the easiest way to do this to give everyone administrator rights..... and, the easiest way to check for this capability is - thru My Computer - navigate to your server’s drive and try to create a file using Notepad - if you can't do it then you've got a problem - turn off ALL locking mechanisms in particular Opportunistic File Locking!!! You can read more about this at Microsoft’s tech support web site of http://support.microsoft.com/kb/296264 - turn off auto disconnect.. This is very, very important. You can read more about this at http://support.microsoft.com/?kbid=297684 and http://support.microsoft.com/default.aspx?scid=kb;en-us;Q138365 in the Microsoft knowledge base. - most network techs agree that mixing versions of Windows is not a good idea - if you are using a printer with its own network card - make sure the driver works with your current vrsion of Windows - turn of synchronous buffer commits - be real careful if you have a virus checker that is constantly active how it interfaces/interferes with Windows and your network - If you have a firewall make sure IT does not interfere with your network - do NOT use “Fast User” switching – for the obvious reason that a user could easily leave the software open when they switch to a different user - turn off the UAC business Windows Small Business server: We’ve been told “off the record” that some release of this software can have issues.. however, we love 2012 R2 And you must use Microsoft Terminal services / remote desktop – it’s virtually bullet-proof. And... In General... Keep a diary of problems such that you can discuss these with your hardware support person; the more information you can give them - the faster they can isolate the problem. Turn off anything that will shutdown any computer - for example, often the power settings will turn off the hard drive after some period of inactivity. This can easily damage data. This applies to ALL computers on your network!!! If you turn off your computers at night - be sure the server is the LAST to be turned off. Now, this is really important... Make sure you have a professional technician; if they do not know about these sorts of things - then you likely need a new tech. Often we have an office tell us "Oh - he has a Phd in Computers or... he works with them all day at work" - and so on; well - unless they are a professional computer technician who works for a computer service company their know- ledge is very specific and limited and not likely able to support you well. You need a well rounded tech not a specialist. If your tech's profession is in the software side of things then it is likely they are not a skilled hardware/network tech. One last thought...... One thing you must never do while your software is running is press the reset button or reboot the computer with the Ctrl-Alt-Delete key combination - this is almost guaranteed to cause data corruption. If your computer "hangs" on a regular basis contact your hardware support person and advise them of this problem - computers are NOT supposed to hang "often." Now, if you MUST reboot then follow this procedure... - get ALL other workstation right out of IFILE/CFILE/VISION+ - be SURE the server is NOT running IFILE/CFILE/VISION+ - then Ctrl-Alt-Delete the "hung" workstation and then shut it down in the usual manner. - Then reboot the server in the usual manner, meaning go to Start then Shutdown. - Then reboot all the other workstations in the usual manner The Last Section: If you find that your system crashes on a regular basis here are some things to consider: - Make sure UPSs are installed. At the very minimum the server, your hub/router/switch and Internet modem must all be on a UPS - Do not use Microsoft's Security Essentials - Make sure all network cards do NOT go to sleep - Disable "Opportunistic Record Locking". In Windows 7 and VISTA you might need to have your network support person do this as a registry patch (we have supplied one just in case they don't have it handy; it’s in the menu you access from the ToolBar using the blue question mark) - Make sure you do not have a virus and be sure your virus checker is up to date. - If you have seen the "blue screen of death" you have real problems; call us and we'll try to "clean" the data corruption - If you think you have data that is permanently corrupted; call us and we'll try to "clean" the data corruption - As a temporary measure: do not have the Internet and this software active at the same time do not have things like MSN, LogMeIn etc. active since the Internet will not be active turn off your virus checker - Be sure the software is being run on an account with Administrator privileges - If you are running VISTA or Windows 7 on the sever try putting the software's \SAM folder in the \PUBLIC folder and re mapping the remote drive to \PUBLIC - Turn off everything that starts automatically.. you can use MSCONFIG to do this - If all else fails reboot the computers in safe mode with network support; if it stops crashing then you know you have a defective/incompatible device driver somewhere - Make sure you are using a mapped network drive to access the software, e.g. F:\SAM\ISAM.EXE Do NOT use indirect mapping, e.g. \\SERVER1\SAM\ISAM.EXE - You could always use Microsoft Terminal services with remote desktop – it’s virtually bullet-proof.