I have installed TD3 and still I can see it run in the task manager. I even updated the run files. The only way I can get it to run is to rename the exe file with it allready running in the backround. Wuz Up?
I start it by double clicking the tds 3 icon and it says it's running in the task manager. Then if I go to the program folder and rename thje exe file and double click then the tds 3 consule comes up. the task manager then says both the renamed and original file are running?!
No the icon does not come up. 10638 K is all that shows up on task manager with no cpu usage. When I re-name and start; I still don't get a task bar icon.
Ensure your system DLLs are up-to-date ... http://tds.diamondcs.com.au/index.php?page=files Regards, Wayne
Hi Bike, did you reboot after installing TDS? which windows version are you running? TDS is set not to be able to run twice, so the renamed exe might explain why it does. Kill that first one if you like so you can get to the configuration settings on the startup tab make sure you select minimize to taskbar or systray and to have it startup normal. (systray gives a small quicklaunch menu on it) Is this the first time you installed TDS or was it normal with icons before? And during the install is asked if you want icons to be created, which you allowed i suppose? Are you running XP with the option to lock the taskbar so no icons can be placed there? (then you should have this with more programs icons) Saw this recently with somebody and no way to get to TDS that way or he had to unlock that taskbar or have the icon appearing in the systray.
And the other questions? did you make sure the taskbar is not locked? And do other programs icons appear there?
I think Wayne had the right solution: so just go here: http://tds.diamondcs.com.au/index.php?page=files
Whether TDS shows up (visibly) shouldn't have anything to do with the filename TDS-3.EXE, but if TDS wont start with this name, its possible a trojan is killing it.. im not sure as your conditions dont seem to sound right ! I would say update the databases, rename TDS-3.EXE to something else and run it, then run a full scan - System Testing | Full System Scan
I've got a really involved question about this. When I do a "Search" for all the .ocx's and .dll's in the list at that link, I wind up with multiple versions of the same file installed at different locations at different times. ( a ) Shouldn't they all be the same (all using the latest version)? ( b ) How do I go about accomplishing that (if I need to do it)? (This looks like - WORK!). Pete
Hey Pete, I'm wondering if the different locations sometimes include application specific directories, beside the normal System32 area? I have several pieces of software that have what appear to be earlier versions of some standard Microsoft .dll files in their own directories. My assumption was that either their software was specifically coded to the routines in that version and couldn't use a newer version, or, perhaps more likely, they included what was a current version of the dlls at the time they built their kits, and these are the minimum versions required to run their software. I don't think that you'd want to go changing the dlls in the application specific directories since this could have unforeseen results in regards to your software working properly.
Yep thats the best way to do things, let programs install a copy in their own folder. Windows XP allows this and automatically keeps a copy of the best file in a special folder - even if you replace the file in System32, it uses the version it wants to.. I forget the name of this system they implemented Theres a folder here - C:\WINDOWS\WinSxS With versions of runtime files. XP users dont ever mess with those..
Sounds interesting, as i'm always carefull with older software to avoid overwriting newer installed files. (win98se) I think installs should always check for what is there and either ask or install necessary versions like your example in their own directory to avoid further messes elsewhere.
Hi Gavin, Is this what you mean? http://www.win2000mag.net/Articles/Index.cfm?ArticleID=38821 Regards, Pieter Note: not the bug of course, but the Windows File Protection
Thank you, all. Really glad that I didn't have to start messing about with that! From what I remember about looking at them yesterday, a higher-numbered version was always the one that was in System32 - in most cases, the version numbers were higher than the recommended minimum's given on the TDS page. Pete