How to install TM5 on Win7 64-bit

Recently installed TM v 5.0 on three new Windows 7 64-bit Dell workstations (hooked into a small domain run by a Dell box running Server 2008). Through an amalgamation of things I’ve read about on this site, referred sites and experimentation, I used the two approaches and put together this procedural doc for the firm I work for.

1.) On new workstation install VFP (visual fox pro). Used VFP6 first. Obtained files from here:

2.) Create a printer called TeleMagic Fax 35:

  • Open the Control Panel & select Devices and Printers
  • Add a new LOCAL printer for this PC
  • Assign it to LPT3
  • Select GENERIC and “Generic/Text” printer driver
  • Name it exactly TeleMagic Fax 35 (including spaces & capitalization)
  • Select to Not Share this printer
  • Select option to not have it the default printer
  • Grant all users full rights to this printer (via printer properties once created)

3.) Browse to location of tm.exe on server and run file.

4.) Select No Database if prompted or just don’t login.

5.) In TM go to File – Workstation Setup and run through process.

6.) Log out.

7.) Copy the spoolss.dll file from the c:\windows\System32 folder to the c:\tm5node folder.

8.) Browse to location of and run “Dbutil.exe” – Copy and Register System Files

9.) Log in to TM.

10.) Confirm Directory is set properly: a. In TM go to: Options – Preferences – Directory: b. Make sure all options for Function Keys, List Boxes and Toolbar Configuration are listed as Global Directory.

11.) On program shortcut created in Step 5, right click and add user initials to end of target line.

 Alternative Method:

1.) Add Administrator account to new computer, and set up on domain using the domain administrator login credentials. Reboot will be necessary.

2.) Log back in as Administrator.

3.) Turn off UAC.

4.) Install VFP (visual fox pro).

5.) Copy the c:\tm5node and C:\Program Files\telemagic (OR c:\Program Files (x86)\telemagic if from an x64 machine) (tm5node contains a bunch of files, telemagic folder contains a fax folder and one other file) from a working computer to the same locations on the new computer.

6.) Copy the spoolss.dll file from the c:\windows\System32 folder to the c:\tm5node folder

7.) Create a printer called TeleMagic Fax 35:

  • Open the Control Panel & select Devices and Printers
  • Add a new LOCAL printer for this PC
  • Assign it to LPT3
  • Select GENERIC and “Generic/Text” printer driver
  • Name it exactly “TeleMagic Fax 35? including spaces & capitalization!!!!
  • Select to Not Share this printer
  • Select option to not have it the default printer
  • Grant all users full rights to this printer

8.) Change all .exe files in c:\tmwin folder to have compatibility mode with Win XP SP3. May need to set as run as administrator as well.

9.) Set permissions on tm5node folder so that all users have read and write access.

10.) Map network drive that contains database files using administrator credentials.

11.) Run tm.exe to see if program loads. If not see below links. If it does, proceed to Step 12.

12.) Create new user account for domain and then log out of Administrator account and back in as standard user account.

13.) Browse to c:\tmwin and create shortcut of tm.exe in the desired location.

14.) Right click on the shortcut and select Properties. In the “Target:” line at the end, after tm.exe put a space and then the users login initials. i.e. c:\tm5node\tm.exe ABC

15.) Map network drive of folder containing database files using standard users’ credentials.

16.) Run shortcut and confirm that program boots properly.

17.) If program does not run properly, see below links.

FaxMan Error: If user is getting a “Failed to open or initialize the FaxMan Database” error then: Set the permissions on c:\program files\telemagic to permit full access by all Telemagic users (or Everyone, if that is easier). To do so, right-click on Start, choose Explore or Windows Explorer. Navigate to c:\program Files. Right-click on Telemagic, and choose Properties. Choose Security, and grant Everyone (or the Telemagic users) full access.

TeleMagic and OPLocks

OpLocks is turned on by default and should be disabled on both server and workstations, see below.

Microsoft about Opportunistic locks and Windows Server 2003

Configuring opportunistic locking in Windows

Error: 1733: Class definition TELEMAGIC.DOWNTIMEMONITOR is not found

This error has to do with the user access rights.

This generally occurs with a new PC, attempting to run TM5 for the first
time. It’s looking for DTMON.DLL in the System32 folder.


Make sure the user has Power User rights and it should work fine.

Either manually copy it into the System32 directory on the PC in question from the server or do this:

  1. Log into the local machine with administrator
  2. Run DBUTIL on the local machine and run Register System Files
  3. Exit out of DBUTIL
  4. Run TeleMagic v5
  5. Exit out of TeleMagic
  6. Log off Administrator and log in as the user
  7. Run TeleMagic v5

When all else fails install an eval copy of TM to a different directory (c:\tm5delete) once installed try running the client again.  Sometimes the eval install seems to do a better job of getting the files registered and setup correctly than copy and register system files does


Error: “an unknown error occurred while loading Tm.exe. shutting down”

I have a client who just bought a laptop with Win 7-32-bit and he gets ‘an unknown error occurred loading TeleMagic. Shutting down.’


Most common error has to do with the fax driver, or the fact that the user doesn’t have rights to update files in the system32 folder.

Check to make sure you have admin rights on the machine, for the first time you run TM.

Log in as the administrator, and run  the copy/register. After that is done, try it again.

When you install TM5 on a W7 or W Server 2008 you must copy from somewhere the telemagic folder that is in c:\program files\telemagic

There are fax files and folder in there that does not get created on install.  If it is a 64 bit OS you would copy it over to the c:\program files (x86) folder.

This telemagic folder is often overlooked because on a XP install we never notice it is there.

If this is a Terminal Services installation, set the Check System Files to N in TM.INI


TeleMagic and 64 bit Windows

Getting TM working on a Windows 7 64-bit computer is very tricky.


The trick is to enable the local Administrator account, change the password of the local Administrator to match the server’s Administrator password, then do the entire workstation setup as Administrator.  Once TM is running, disable the local Administrator.

Just built a new system with 64-bit W7 Pro, turned off UAC, created the TM print driver and the TeleMagic folder in Program Files, then did a copy/paste of the TM folder to the new system.  TM fired off with no problems.

TM5 SP4 runs fine standalone on my Win 7 64 bit installation.

Need to live with or address the Faxdriver issue on startup.  Issues I had which I thought were Win 7 security UAC etc turned out to be Kaspersky antivirus.

Just in case anyone is doing anything with TM and ODBC. Microsoft’s ODBC drivers do not work in a 64 bit environment. However you can get the Advantage Database VFP ODBC drivers from Advantage for free and they work just fine with a 64 bit OS.

Here is more information and also some talk in the comments section on the
Advantage ODBC driver.

Open any DBF file with a 64 bit machine in Excel you will probably have a problem as the VFP ODBC drivers don’t work in windows 64 bit.

Windows 7 64-bit is great but stick with Office 32-bit. The ONLY reason for a 64-bit version of Office is to work on very HUGE documents.

TeleMagic DOS

TeleMagic DOS does not work on any 64-bit computers as no DOS programs work on a 64-bit computer. However, it will work under a 32 bit OS (WinXP Pro SP3) and a 64 bit chip under a VMWare image.


Error: 1104 / 1105 – Proc

The large majority of 1104 / 1105 errors experienced have been network related.

“The error message indicates that the specified file is not available. There are several possible causes, but the most likely would be that the file is being locked by some other operation, or that the paths are incorrectly mapped.”

  • Check components like hubs, nic card on the server, switches. Also check to see that TCP is the only protocol running. NETBEUI & IPX have caused this problem in isolated cases.
  • In Windows 2000 environments, missing patches to Terminal Services have proven to cause this error as well.
  • This is a general Error Reading File message. You need to check the typical things (server error log, disk space, temporary files, permissions, etc). You might try copying the installation to your local system, doing a Path Update, and then seeing if you can create the problem on the local system.
  • One thing to be aware of in Win7. I’m not sure if this is all the time, but if you run something “as administrator”, it won’t pick up the drive mappings you have in place. I don’t know if that would effect this or not.
  • Could a virus scanner be running and locking the file?
  • You have a bad port on the switch.  Plug the network cable from that machine into a different port.
  • Make sure they are running from a node install. Try running some network tests, to see if there are errors occurring.
  • I had that problem with a machine in my office recently.  I replaced the network cable from the machine to the wall and its worked perfectly since then.

Error: C0000006

Unknown Error C0000006

This is generally caused by the Terminal Services problem for which there is a patch offered by Microsoft. This appears to be the fix that prevents corruption to the Visual Fox Pro DLL files held on the server in the \SYSTEM32\ folder. The files in question are vfp6r.dll and vfp6renu.dll.

If you are getting this error, you need to fix it and then prevent it from recurring by applying the MS patch.

The fix is to delete those files from \SYSTEM32\ and replace them with those stored within TM. To be safe you might want to rename rather than delete these files. We suggest that you perform a full backup before proceeding.

  • All users need to be out of the system
  • A Rebuild is not required.
  • Log in as a network operating system supervisor
  • Delete (or rename) vfp6r.dll and vfp6renu.dll in \SYSTEM32\ using Windows Explorer
  • Close DBUTIL.
  • Test for the error

Note that you can work around the problem by having ALL TS users log off TS & return to TS & TM. This works for a random period depending on usage of TS.

TeleMagic on Windows 7

Installing TeleMagic on Vista and Windows 7

Let’s make sure we all understand something here.  Windows Vista/7/8 is not Windows XP.  Each user runs in their own virtual space where in XP every user ran in a common space.  So with Windows V/7/8 when you say “Run as Administrator” it literally creates a new namespace and environment for the user Administrator and does NOT share any common environmental space (mapped drives, printers, etc…) with the local user already logged in.

This is why the first step in any Workstation setup is to log in as Administrator.  Not a user with Administrator rights, not a user who has Power User rights, but the actual Administrator.  If it’s a domain, then log in as <domain>/Administrator as the username.  If it’s a workgroup machine, then enable Administrator then log in as Administrator.

  • In order to get Win 7 to run TM I had to use XP compatibility mode. Run it as Administrator. Mark all .EXE files as compatibility.
  • I am able to run TM5 on Windows 7 without any compatibility mode settings.  It is easier on a domain network than a workgroup network though.
  • I have TM running locally on Windows 7 in compatibility mode.  However, I can’t get it to run across the network.  It’s a little peer to peer with an XP machine as the server.  When I go across the network and set compatibility mode then try testing, I get a generic “TeleMagic has a problem and is shutting down” error.
  • The only way to get TM 3.5 to work with Windows 7 is with the compatibility checkbox.
  • I just got done trying to make it work on 2 Windows 7 machines — one set up as a workstation and one as a workstation/server.  Not an ideal situation, but it has worked for them under Win2K and XP. After creating the fake printer and setting it to run as administrator, TM works fine on the host machine with TM in a shared drive.
    I installed a node to the C: drive and it still ran fine.  I thought I was 3/4 done. The workstation however would not run TM.  When starting it from the mapped share, run as administrator, it comes up with the ‘System ID not defined . . .’ Starting a command prompt: type t:\tm5\programs\tm.ini from a local prompt types the ini file fine. Now the weird part, if I let Win7 diagnose the problem, TM starts and runs fine.  The diagnostic wizard then comes back and says TM is an incompatible program!  Being a lover of a good joke, I thought that I would install the node as long as it was running.  I did, it did, and it attempted to restart from the node — system ID not defined etc etc.  That’s all I could get it to do when running from the node install, even with running the fixit wizard.  It’s like it won’t see the external mappings (or mappings to non-local drives) from within the program. Just to be sure, I shared a drive on the then workstation machine, copied TM5 over and reversed the roles.  Same symptoms, other machine all around. I’ll try it with TM resident on a real server OS tomorrow after I get a Win7 workstation set up at the office to see if it is just a peer to peer killing design bug.  I couldn’t find (or Google or Bing) any references to a files= statement or config file in Windows 7 either.  There is no config.nt file. This is too simple … but did you look to see if the TM ID’s in tm.ini are the same and consistent with the install?  I remember a issue like this way back that was caused by one of the ID’s being changed by some other program. This is a stupid question, but are they trying to use Windows 7 Home? If so, that might be your problem.

Bottom line:

  • Windows 7 32 bit — The server in use does not seem to be relevant, just the workstation running TM.  I did not test ANY ‘home’ versions.  All Pro and I tried both simple shares and domain accounts.  All the same results.  The wizard that I was using is the Windows 7 compatibility wizard.  It only seems to fix a W7x64 to W7x64 issue but I didn’t try 64 bit w/s to 32 bit W7 server.  No point since the ‘fix’ just gets you in the once. I have now tried at 2 different sites and have not been able to get it to start on the 64 bit version of Windows 7 on a share.  System ID not defined or blank.  It will run fine off the C: drive.

I just talked a client thru getting Telemagic running on a Windows 7

  • Ultimate 64bit workstation. The environment is as follows:
    • Server:  Win2003 Server (Domain Environment)
    • Workstation: Windows 7 Ultimate 64bit
    • We ran thru several steps, but I think the main ones were:
    • Create a printer called TeleMagic Fax 35, and give everyone full rights.
    • Run DBUTIL Copy and Register. If you can’t get this to work while running it from the network drive, copy the installation to the local system to run it. It will have to be run with Administrator rights. When we ran this, it hung up while it was doing something with VFP6R. We killed it after a couple of minutes, and continued, and it seemed
      to work OK. This may be something that will occur at other sites, or just something about our site.
    • You may need to have a node install to run it. We made a node from the local copy of the installation, then changed the tm.ini in the c:\tm5node folder to point to the network installation.

We did get one strange error, at one point. It was saying that Spoolss.dll wasn’t found, and Telemagic exited. We then did the copy and register, and copied the spoolss.dll from the system32 folder back to the Telemagic programs folder on our local copy. Later, we tested, and found that this step was not necessary. I think it had something to do with the copy and register not being run. I’m going to test this with one more workstation, and then I’ll try to document something a little more formal. In the mean time, if anyone has the ability to test this, please do so.

  • Try the node install while accessing Telemagic via the network on Win7 64bit. BTW, after we got in fine with the node install, the client said that they tried it using the original shortcut, which went directly to the network programs folder, and that worked, as well. Go figure… The client did get some User Account Control messages the first time or two that they ran Telemagic, but after that it went away. This may be due to Telemagic changing the system time format. After further review, here are the steps we think you need to take to get Telemagic working on a network on Windows 7 64bit:
    1. Map the drive letter.
    2. Run the command prompt, with administrator privs.
    3. Map the drive letter again in the command window, using the Net Use
      Net Use T: \\server\share
    4. Run Database Utilities via the command window, and do the Copy &
      Register from the System menu (no need to log in):
    5. Create a printer called TeleMagic Fax 35, with full rights to
    6. From the command window, run Telemagic to do the Workstation Setup:
    7. Go to File/Workstation setup, and take all the defaults (leaving
      the userid/password blank).

Once the above is complete, you should be able to access Telemagic via the node shortcut on the desktop. If anyone encounters any issues with this, please let me know.


On my freshly reinstalled Windows 7 RC 32-bit laptop, the code that launches SendMailToQueue does not produce any errors at all, however nothing gets populated in the TMFAX1 table.

The SendMailToQueue creates a header record with a unique mail key in it.  I’m not sure how that all works, but I did come up with another solution that I’m going to work on.

Since my TMAS works within a Windows 2000 Server VM, I’m going to write a program that runs on the Windows 2000 Server VM that looks at another table and will execute the  SendMailToQueue when a record gets populated.  So instead of executing SendMailToQueue on each workstation, I’ll write a program that writes to this temp DBF file instead so the program on the Win2K Server will execute the SendMailtoQueue command itself.

Does TeleMagic run on a 64-bit Windows Server? Windows 2008?

I have it running on Windows 7 (64-bit), and just selected Windows XP compatibility.  Chances are very good that it runs on Windows 2008, as well, since Microsoft seems to take some pains in running “legacy” software.

  • Mark all .EXE files as compatibility and run as administrator?  So far that has solved all of the issues for me with TM and Windows 7.
  • An experienced MSCE said that there was an unfixable issue with some legacy applications on Windows 7.  Waiting for SP1 for Windows 7 to see if it’s fixed, but in the meantime, the only solution is to download and install Windows XP Mode and Windows Virtual PC from Microsoft website, and run the app on that.