Compile Never Finishes [Archive] - ForumsHQ
Compile Never Finishes [Archive] - ForumsHQ
Yeah, Im having a problem with my NMR Compile finish itself. I added some rooms to map 16 (All the editing is right version, no errors until now) and when I added this new area (appx. 200 rooms) to Map 16, the compile ability started acting wierd. Usually when I compiled i would get to about 20,000, 25,000 on wccmp002.dat and then it would be finished. Instead it has NO CAP whatsoever and just keeps going and going. I let it run all the way up to 99,999 just to make sure. It crashed my board and corrupted my database but luckily MajorMUD recovered from it. But If I cant compile updates, then I cant do much.. Any answers?
Re: Compile Never Finishes [Archive] - ForumsHQ
possibly try adding the rooms to a different map. make sure none of them are overlapping existing rooms.
Re: Compile Never Finishes [Archive] - ForumsHQ
it sounds like you are working on live dats (using NMR pointed to your BBS directory while the BBS is running)? this is highly unrecommended. read up under the general help on editing scenarios).
to address what is happening though, are you waiting for the update file to finish running through? cause you need to make sure the "Automatic Database Update Complete" message shows up in the audit trail before you can compile a new update. otherwise, majormud is still using the file and then weird things like that start happening. if you're using the old console window i think the lines just show up as "MajorMUD Notice" in the audit trail. you have to actually go into the remote sysop menu and view the end of the audit trail to see what the actual notice is (i think "MajorMUD Initialized" and "Automatic Database..." both show up as "MajorMUD Notice" in the old styile console window.
however, my update file code shouldn't keep counting like that even if this is the case. it has to pass a insert operation and a getnext operation successfully before it will increment to the next number. the only thing i can think of is btrieve is getting all messed up when two programs are dealing with the same file and errors aren't being generated (why this editing scenario is not good).
if this isn't your editing scenario, let me know how your setup is and we'll go from there.
to address what is happening though, are you waiting for the update file to finish running through? cause you need to make sure the "Automatic Database Update Complete" message shows up in the audit trail before you can compile a new update. otherwise, majormud is still using the file and then weird things like that start happening. if you're using the old console window i think the lines just show up as "MajorMUD Notice" in the audit trail. you have to actually go into the remote sysop menu and view the end of the audit trail to see what the actual notice is (i think "MajorMUD Initialized" and "Automatic Database..." both show up as "MajorMUD Notice" in the old styile console window.
however, my update file code shouldn't keep counting like that even if this is the case. it has to pass a insert operation and a getnext operation successfully before it will increment to the next number. the only thing i can think of is btrieve is getting all messed up when two programs are dealing with the same file and errors aren't being generated (why this editing scenario is not good).
if this isn't your editing scenario, let me know how your setup is and we'll go from there.
Re: Compile Never Finishes [Archive] - ForumsHQ
Yeah, Syn is right..in the old style, they both show up as 'MajorMUD Notice'...the way to tell them apart is, after the first 'MajorMUD Notice', the startup lag will go away..the Automatic Database Update doesn't lag the server, and will eventually pop up on the screen..you'll have to watch for it because you won't notice a change to hint that it's done..
Re: Compile Never Finishes [Archive] - ForumsHQ
Well I have NMR pointed in my C:/MUDEDIT directory which is the directory i do all my edits from. I think I did accidently compile an update from the WG directory and that might be what happened. Anyways, I found a backup of my wccmp002.dat file, copied it over and compiled a new update, Everything runs smoothly and it even finishes compiling, Just looks like Ill have to do that area over again.