Maybe this needs to be cleared up... When you compile the mud in linux and you now have an executable, you can not take that executable and run it in windows, and vise versa. (believe it or not, this has to be pointed out sometimes) The unlimited bit system has nothing to do with accessing mem addresses that windows can't hit. Trust me, I should know. Last I checked, quickmud w/ unlim bits compiled clean out of the box. From one of the previous posts, it read like Dantin was typing 'rom.exe 9000' within gdb... you need to type 'run' and then the arguments e.g. 'run 9000'
> Nobody told me I had to go into console and type what you suggested > before run (port #). The only problem is its not crashing.. Or is that a > on windows just to utilize unlimited bits. Why is it that it once > compiled it will not run under windows? Well thats my question. Thanks So, you think that you use cygwin to compile the thing, go through all that trouble and then, you can't even use it under windows? Uh huh... > program=C:\QUICKMUD\AREA\ROM.EXE cs=017F ds=0187 es=0187 fs=5AAF Who would want to go through the trouble of moving their exe over to the area folder every time you made it? Let alone care to... (yes, I know...just stick it in the makefile, etc) I just like my exe in the src folder...keeps things nice and segregated. Ammaross Danan
