CD Key not working in CUT2

Bludra · Post by **Bludra** » Mon Apr 18, 2005 10:31 am

I installed CUT2 and played with mutator, later tried gametype but UT2004 kept crashing when I quit. That means, it could not switch to CUT. I created a shortcut for it, but that ends with message "your CD Key is not valid".
UT2k4 runs normally. Could someone help me?

TKATK · Post by **TKATK** » Mon Apr 18, 2005 12:18 pm

hmm,could you try again,show the log,show the size of ChaosUT2 folder

Bludra · Post by **Bludra** » Mon Apr 18, 2005 2:21 pm

Directory is unaltered, size 547 812 667.

Log: Log file open, 04/18/05 12:12:13
Init: Name subsystem initialized
Init: Detected: Microsoft Windows XP 5.1 (Build: 2600)
Init: Version: 3355 (128.29)
Init: Compiled: Feb 15 2005 17:04:22
Init: Command line: -MainMenuClass=ChaosGames.ChaosGUI_MainMenu log=ChaosUT.log -mod=ChaosUT2 -newwindow
Init: Character set: Unicode
Init: Base directory: D:\UT2004\System\
Init: Ini:..\ChaosUT2\System\ChaosUT2.ini UserIni:..\ChaosUT2\System\ChaosUT2User.ini
Init: Build label: UT2004 Build UT2004_Build_[2005-02-15_17.02]
Init: Object subsystem initialized
Init: Computer: GOTREK
Init: User: Bludra
Init: CPU Page size=4096, Processors=1
Init: CPU Detected: Unknown processor (AuthenticAMD)
Init: CPU Features: MMX SSE
Init: CPU Speed=2009.139227 MHz
Init: Memory total: Phys=522992K Pagef=1275788K Virt=2097024K
Init: Working set: 32000 / 159000
Init: Physical Memory: 510 MByte
Init: D3D Device: Video memory on board: 122 [128]
Exit: Preparing to exit.
Log: Purging garbage
Log: Unbound to Window.dll
Log: Unbound to Core.dll
Log: Unbound to Engine.dll
Log: Garbage: objects: 418->0; refs: 0
Exit: Object subsystem successfully closed.
Exit: Exiting.
Log: FileManager: Reading 0 GByte 5 MByte 713 KByte 1007 Bytes from HD took 0.006000 seconds (0.006000 reading, 0.000000 seeking).
Log: FileManager: 0.033000 seconds spent with misc. duties
Uninitialized: Name subsystem shut down
Uninitialized: Memory Allocation Status
Uninitialized: Curr Memory 0.099M / 0.434M
Uninitialized: Peak Memory 0.576M / 2.688M
Uninitialized: Allocs 9 Current / 3624 Total
Uninitialized: Log file closed, 04/18/05 12:12:15

When I quit UT2k4 or FragOps, windows XP shows blue screen (BSOTD?)
and it says something about IRQ read and write.

CUT doesn`t even start.

jb · Post by jb » Mon Apr 18, 2005 2:47 pm

That looks like the normal ut2004.log? If it was can you find one in your chaosut2\system folder (chaosut2.log)?

TKATK · Post by **TKATK** » Mon Apr 18, 2005 2:51 pm

a bit smaller than mine,but guess thats becouse mine is edited

Does it show cd-key invalid EVERY time you boot it?

i suggest you ask about on the ATARI forum about the BSOD problem,sounds pritty serious(burning hardware,virii or messed up drivers...i guess)

try deleting ChaosUT2.ini and ChaosUT2User.ini in UT2004/Chaosut2/System(doubt it will help,but worth a try)

Bludra · Post by **Bludra** » Mon Apr 18, 2005 3:11 pm

That worked, CUT now runs. But now I am wxperiencing problem that already appeared here somewhere...
When I (finally) got into duel, it did not respond to keyboard or mouse.
Anyway, thanks, I`ll look for next solution elsewhere.

jb · Post by jb » Mon Apr 18, 2005 3:20 pm

you may have to rebind some of your keys...

but let us know!!

Bludra · Post by **Bludra** » Mon Apr 18, 2005 3:24 pm

Heh I had to rebind them

glad that I didn`t have to reinstall all those thingies like that guy...
I was confused because even my mouse was not responding.

Bludra · Post by **Bludra** » Mon Apr 18, 2005 4:14 pm

When I Alt+Tabbed back, it showed BSOTD with error "IRQ_NOT_LESS_OR_EQUAL". I tried to make some changes in Bios settings but it had no effect.
It shows only when I end game and then I have to reset my computer, or when I Alt+tab.

TKATK · Post by **TKATK** » Mon Apr 18, 2005 6:03 pm

reinstall DirectX
Install the newest drivers for your vid
I suggest you find a ram checking/Comp temperature showing program,that might be the key
Does it happen on other gamess?

MassChAoS · Post by **MassChAoS** » Mon Apr 18, 2005 8:23 pm

That BSOD is very likely to be a hardware issue. If it is happening when you close or alt tab, it is most likely to be your vid card. Try DirectX and vid card drivers as TKATK recommended.