database corruption [Archive] - ForumsHQ

[Hobo_Bill]

Whew, sure glad you warned me. I'm such an upstanding citizen and all, wouldn't want to mess that up, ya know.

[FreeBander]

yea i have a modified dll but believe that is the problem it is a poor cracked one. And of corse this is all being done for medical purposes, ahh to monitor the effects of stairing at a computer screen for endless hours, yea yea thats the ticket !

[Hobo_Bill]

I coulda sworn my dll was cracked, dunno how it got that way but it was.

[Hobo_Bill]

Now is there some big problem with running an i dll with j dats? I'm doing it currently and having no problems besides not being able to edit anything of any consequence. But that's not because of the version difference, it is, as previously said, because of an uncracked or poorly done job of cracking the dll. Can't find anything anywhere. Got current .dll off of an ftp that said it was cool, but doesn't work. See if I get editted ;)

[syntax53]

Originally posted by Hobo_Bill

Now is there some big problem with running an i dll with j dats? I'm doing it currently and having no problems besides not being able to edit anything of any consequence. But that's not because of the version difference, it is, as previously said, because of an uncracked or poorly done job of cracking the dll. Can't find anything anywhere. Got current .dll off of an ftp that said it was cool, but doesn't work. See if I get editted ;)



yes, there is a very big problem running an i dll on j dats. the majormud dll is basicly all the majormud code. so any code changed from i to j (a shit load) are lost by doing that. it may work, but you aren't getting anything from actually having J installed besides dat changes.



-syn

[Hobo_Bill]

alrighty.. new to the whole thing.. Thanks syn.