RBT 1.0.5 produces a RegCreator.exe error when trying to register it!

Done :)

Oops forgot to mention I'm running Windows XP Pro 32-bit fully patched (partly thanks to AutoPatcher)

The registration information is correctly recorded in the registry, it's just this new RegCreator.exe is having problems reading it!

Could we change the registration system to be more like Rival Ball's?

Ok, I've downloaded shorter versions of the REG filenames and while I still get the error in the screenshots I sent you, RBT is now registered!

Thank you!

Nope, the registration isn't holding when you quit RBT altogether and reload it's unregistered again!

Yes, these newer versions seem to fix the problem nicely! (I'm calling them 1.0.5a)

Thanks again :)

One other thing, the freeware board sets appear to be missing from the Registered version of RBT!
They were available in v1.0.2 but not in v1.0.5, any chance they could be re-included?

To Other Players:
These new versions appear to store their settings in C:\Documents and Settings\<username>\Application Data\Longbow Digital Arts which means you can no longer run multiple copies of Rival Ball. I love it :)

Thanks once again, I appreciate it :)

Problem... after upgrading to the new version, I can't seem to get into Campaign mode without it erroring out and crashing.

jujaga, is this RBT or Tread Marks?

Oops... I forgot to type in RBT... phoridian slip... durr...
I tried copying a memory dump, but I guess it didn't work out correctly.
I can confirm that it is repeatable on my end, so either it's my computer at fault or maybe there's something in the coding. Either way, when it errors, it references itself as the error... rb tournament.exe. The error happens when i click on campaign mode and it loads the screen. It does load the screen but right afterwards it errors. It's as descriptive as I can make it for now...

I've posted a PM to you. After doing a bit of other testing around, I think the problem may be with the frame rate counter in the game and that it somehow conflicts with the campaign mode when it's enabled. It appears to work fine when there is no counter.

You're not suppose to play games with DirectX's frame counter enabled all the time, it's only there for diagnostic purposes!

True, but even so, the diagnostics are there for paranoid people like me who like to have every aspect of their computer the way they want it... but that's not the point.
My main point is that the counter apparently is the source of crashing in the campaign mode... at least on my computer to my knowledge. Now, for being a diagnostic, it isn't supposed to interfere with the actual game itself, but it is obviously having some unwanted side effects. The reason I raised this issue up is because it appears to be a bug in the coding which did not exist in the 1.0.2 version. I know there are people out there who love to see what their frame rate is and are completely obsessed about it, like I am. It isn't a bad thing to know the performance of the computer at the moment, but again, this was only raised because of a bug issue.