FORUM HOME > TNM > Help
Windows XP Problem!!

kingsopranoPosted on 04/11/03 at 06:27:41

every time i try to load tnm i get and error message for dos...memory manager loaded..xms drivers not installed
then it just goes to loading database and does not leave that screen

i cant play anymore on xp pro...anyone else have this or know what i can do???

it usedto work fine
CarlzillaPosted on 04/11/03 at 06:43:14

ctrl-alt-delete and close the http-get.exe from the processes list...do this twice and it will work fine.
Tom_ImpPosted on 04/11/03 at 22:36:37

I'm getting a new computer in a few weeks with Windows XP Home on it. Is there anything I have to set up before running TNM so I don't encounter all these problems I keep reading about?
pszPosted on 04/12/03 at 05:52:37

"All these" problems?

This is really the first "major" problem I've ever seen in TNM using XP. And if you don't mind waiting a couple of minutes every once in awhile, it won't affect anything.

The only other "issue" is the Invalid Data - ACTIONS.DEF you'll get before a match (It will quickly be overwritten by match text). Oliver has said this doesn't actually affect anything, either.

So really, aside to mild annoyances(at worst), TNM runs in XP just fine. No need for compatibility modes or anything else.
Oliver CoppPosted on 04/13/03 at 12:56:33

Just add the line

DisallowDBChecking=1

to TNM.CNF and the issue will disappear for good.
Fighter_HayabusaPosted on 04/14/03 at 17:49:47

On 04/13/03 at 12:56:33, Oliver Copp wrote:Just add the line

DisallowDBChecking=1

to TNM.CNF and the issue will disappear for good.
How do I do that?  I found that file, but I can't do the "Open With" to open with notepad.

FH
LillaThrillaPosted on 04/14/03 at 19:31:29

Try opening Notepad first then doing a File -> Open from within Notepad.

Files with a CNF suffix are usually associated with another Windows program, hence the lack of an Right Click -> Open With option.
Oliver CoppPosted on 04/24/03 at 18:44:54

Or just install the Build 6d patch, that removes the database checking feature which is causing the problems you mentioned in some XP and 2K installations.