Re: Windows update may have broken SwiftForth and SwiftX!? (TTY. DLL)

From: Bulgrien, Kevin <Kevin.Bulgrien_at_GDSATCOM.com>
Date: Mon, 17 Nov 2008 10:19:37 -0600

Regarding an old, 2006 case of the "deleted" TTY.DLL, thread here:

  http://www.forth.com/archive/swiftx/2006/0582.html

As a result of a similar experience with a project that is a number of
years old, I propose that there is a distinct possibility that the
"problem" was not that the TTY.DLL file was deleted by some other
software, but rather that old versions of the SwiftX installer put
TTY.DLL in C:\WINDOWS\system32 and that the developer may have
attempted to reuse an older installation after a workstation change.

I got the inexplicable TTY.DLL missing error when I went to work with a
product that had been built and released using 3.2.2. I wanted to do some
work with the old installation (due to various reasons), and had a preserved
copy of the installation in use when the product was in active development.
Since that time, I got a new PC and had installed a newer version of SwiftX,
but had never re-installed 3.2.2. I slipped the 3.2.2 installation into the
appropriate path, and got the TTY.DLL error upon trying to open the project
file. Having read this thread, thought I may have been similarly bitten by
an IT protection mechanism. Since this product used more than one
processor,
and had some other bizarre issues, I went to backup rather than doing a
fresh
install of the toolchains. I went to restore backups of the preserved
installation directory, and found that TTY.DLL had never ever been installed
in the Bin directory.

I obtained the appropriate TTY.DLL file by re-installing the old installer,
and found that it had been installed into C:\WINDOWS\system32 instead of in
the SwiftX Bin directory.

All that said, please do not read this as advocating use of old versions of
SwiftX... In our case there exist extenuating circumstances (which are
less than ideal) that seem to make it reasonable to use the older toolchain
despite the fact that new versions will have bug fixes that we seemingly we
ought to take advantage when we reopen the old project. I would not be
surprised if the original poster had found himself in a similar situation.

---
Kevin R. Bulgrien
Design and Development Engineer
This email message is for the sole use of the intended recipient(s) and may contain General Dynamics SATCOM Technologies confidential or privileged information.  Any unauthorized review, use, disclosure or distribution is prohibited.  If you are not an intended recipient, please contact the sender by reply email and destroy all copies of the original message.
----------------------------------------------------------------------
swiftx_at_forth.com          The SwiftX programming discussion email list
To unsubscribe, send subject "unsubscribe" to swiftx-request_at_forth.com
For list command help, send subject "help" to swiftx-request_at_forth.com
Message archives are located at http://www.forth.com/archive/swiftx
----------------------------------------------------------------------
This list is a forum for SwiftX users.  For product support and bug
reports, please send email to support_at_forth.com
----------------------------------------------------------------------
Received on Mon Nov 17 2008 - 08:16:36 PST

Subscribe to our e-mail list service. It's free for all SwiftForth and SwiftX users!

This archive was generated 07-Feb-2012. Archive updated nightly.