Page 1 of 1
I know I have got to be missing something
Posted: Mon Mar 01, 2004 9:59 pm
by an00bis
I have read the manual, looked over all these topics, but still can't figure how to use the thing. I run MQ2, its down in my tray and all, and then in game, it acts like nothings there. What am i doing wrong?
Posted: Mon Mar 01, 2004 10:09 pm
by Raging_Goblin
See that link up there that says Search? Try it out, it's REALLY helpful. This same exact question has been answered, what, so many times it's sickening?
Posted: Mon Mar 01, 2004 11:30 pm
by an00bis
Ok, so I read how I start using it, and nothing works. So since nothing works, I am guessing you can still have MQ2 running down in the tray, but the compile could still be wrong. So should I re-compile?
Posted: Tue Mar 02, 2004 8:10 am
by Raging_Goblin
Compiling instructions
BEFORE COMPILING WITH ANY METHOD - Run MQ2Auth.exe (NOTE: IF YOU ARE COMPILING FOR SOMEONE ELSE, THEY NEED TO RUN MQ2AUTH.EXE. THE FILES MQ2AUTH GENERATES ALLOWS MQ2 TO RUN ON THE COMPUTER IT IS GENERATED FROM. THE GENERATED FILES CAN ALLOW MULTIPLE PEOPLE TO RUN THE SAME COPY, SEE THE COMPILING FOR FRIENDS TOPICS)
Visual Studio 7 / .NET - Select "Release" configuration (should be already set), hit Build All. All DLLs and the MacroQuest2.exe will compile to the release directory.
Visual Studio 6 - Load the workspace. Set MQ2Main as active project. Hit Build MQ2Main.dll (F7). Now do Batch Build (under Build menu). Make sure everything in the batch build window that says "release" has a check by it. Click Build in the window. All should compile with no errors or warnings.
So... yeah, did you FOLLOW ALL THOSE DIRECTIONS?!
GO HERE for the rest of the post. READ IT ALL MANY TIMES!!
Re: I know I have got to be missing something
Posted: Tue Mar 02, 2004 8:21 am
by wassup
an00bis wrote:I have read the manual, looked over all these topics, but still can't figure how to use the thing. I run MQ2, its down in my tray and all, and then in game, it acts like nothings there. What am i doing wrong?
The first thing I check when this happens to me (when I am very tired usually) is to make sure I have all of the needed files in the Macroquest 2 directory. Takign a look at the readme.html in the releaase folder will show you which ones.
It might not be your problem, but it wouldnb't hurt to check for those files, especially eqgame.ini and Macroquest.ini
Posted: Tue Mar 02, 2004 11:52 am
by mcswanbeck
I had the same problem once and found out that I had to clean up some files first. The same problem was at a few of my friends.
Anyways, following the below steps works for me everytime:
Visual Studio 6:
- Run "MQ2Auth.exe"
- Load the workspace.
- Set MQ2Main as active project.
- Choose "Batch Build" from the Build menu.
- Click "Rebuild all".
- When that is done, press F7 to build MQ2Main.dll.
- Run "/Release/MacroQuest2.exe"
Posted: Wed Mar 03, 2004 2:38 pm
by TheWarden
Or the idiots way(the only way i can use
):
1.) Double click MQ2auth.exe
2.) Double click dsw file
3.) Go to build and select batch build
4.) Select OK, wait till done and close VS6
Same thing tho :)
I'm a tard.
Posted: Mon Mar 15, 2004 7:24 pm
by MichiganMan
I can't seem to get this to compile without getting invalid Library errors. I am running the MQ2Auth.exe.
I know this has something to do with an inproper CVS config, but I can't seem to get it right, and a search of the site hasnt found any answers other than, to search the site more.
I am using VS6.0.
*dons flame reardant Underoos!!
Posted: Mon Mar 15, 2004 7:32 pm
by Lax
To start with, you shouldnt be using CVS. Download the zip from the download page, and read the thread you should be reading...
Posted: Mon Mar 15, 2004 7:47 pm
by MichiganMan
I did download the zip. I read the reading...I followed all the steps. My RESEARCH from the searches told me that it was/is a CVS error. So I was wrong in this assumption. I am still having the same issues.
I have tried doing a clean build. I am still having no luck.
Posted: Mon Mar 15, 2004 7:54 pm
by dont_know_at_all
Post less information.
Posted: Mon Mar 15, 2004 7:59 pm
by MichiganMan
--------------------Configuration: MQ2Main - Win32 Release--------------------
Compiling...
EQClasses.cpp
MQ2Auth.cpp
MQ2Benchmarks.cpp
MQ2ChatHook.cpp
MQ2CleanUI.cpp
MQ2CommandAPI.cpp
MQ2Commands.cpp
MQ2DetourAPI.cpp
MQ2DInput.cpp
MQ2Globals.cpp
MQ2KeyBinds.cpp
MQ2MacroCommands.cpp
MQ2Main.cpp
EQLIB_EXPORTS
MQ2Mouse.cpp
MQ2Parms.cpp
MQ2ParseAPI.cpp
MQ2PluginHandler.cpp
MQ2Pulse.cpp
MQ2Spawns.cpp
MQ2UserVars.cpp
MQ2Utilities.cpp
MQ2Windows.cpp
Linking...
C:\Program Files\Microsoft Visual Studio\VC98\LIB\LIBCMT.lib : fatal error LNK1113: invalid machine type
Error executing link.exe.
MQ2Main.dll - 1 error(s), 0 warning(s)
Posted: Mon Mar 15, 2004 8:06 pm
by Lax
Linker Tools Error LNK1113invalid machine type type
The machine type specified in the object header is not valid.
Possible cause
The file is corrupt.
Rebuild the object.
See Corrupt Object File for more information.
corrupt object file:
Sometimes the linker is unable to process your object files because they are corrupt. Besides the usual causes of corrupt files such as network problems or exposing a floppy disk to a magnetic field, sometimes the compiler writes an incorrect object file, which you should report to Microsoft Product Support Services.
After you have ruled out a hardware, operating system, or network problem as the cause of the corrupt object file, you should try the tips below. Changing compiler options and recompiling sometimes causes the compiler to write a non-corrupt object file.
Possible solutions
Turn off optimization with the /Od (Disable) option.
Disable minimal rebuild with the /Gm– (Enable Minimal Rebuild) option.
Compile with the /Gy (Enable Function-Level Linking) option to package functions.
Use a different code generation option. See the /G (Optimize for Processor) options.
Change the order of functions and global variables.
source: (in dev studio) Help->Index, type "LNK1113"
Posted: Tue Mar 16, 2004 5:52 am
by mcswanbeck
MichiganMan wrote:Linking...
C:\Program Files\Microsoft Visual Studio\VC98\LIB\LIBCMT.lib : fatal error LNK1113: invalid machine type
Error executing link.exe.
... and you are sure that all intermediate files and output files were deleted before you started to compile?
I have had some odd errors when try to move the source code from one comp to another when I didn't clean up those files first.
Posted: Tue Mar 16, 2004 12:21 pm
by MichiganMan
I finally was able to log in to the Trial version of VS.NET and get it recompiled at 6am today...then I see there was a patch. ARRRGH.....
