Log in

View Full Version : Symbol Loader not loading from CL


micmic
May 1st, 2004, 06:47
CL=command line. When I write "loader32 myapp.exe" (either from "myapp.exe" directory or from Symbol Loader directory), Symbol Loader window appears but it says "No Module Opened" and of course the program is not loaded. Now, if I use the menu from the Symbol Loader GUI, file opens without problems and breaks in at WinMain as it should.

I use Softice from DS 2.7 with nmtranspatch applied. The above problem is very annoying because it destroys my one-click debugging of my own apps.

So, why doesn't SL work from command line ?

Thanks

naides
May 1st, 2004, 07:13
Quote:
[Originally Posted by micmic]CL=command line. When I write "loader32 myapp.exe" (either from "myapp.exe" directory or from Symbol Loader directory), Symbol Loader window appears but it says "No Module Opened" and of course the program is not loaded. Now, if I use the menu from the Symbol Loader GUI, file opens without problems and breaks in at WinMain as it should.

I use Softice from DS 2.7 with nmtranspatch applied. The above problem is very annoying because it destroys my one-click debugging of my own apps.

So, why doesn't SL work from command line ?

Thanks



Using Symbol Loader From a DOS Prompt
Symbol Loader (LOADER32.EXE) supports a command-line interface that lets you use many of its features from a DOS prompt without viewing Symbol Loader's graphical interface. Thus, you can automate many of the most common tasks it performs.

Before you use LOADER32.EXE from a DOS prompt, use Symbol Loader's graphical interface to set the default search paths and to specify translation and debugging settings for each module you plan to load. Symbol Loader saves these settings for each file and uses them when you use Loader32 to load or translate files from a DOS prompt.

To run LOADER32.EXE, either set your directory to the directory that contains LOADER32.EXE or specify the SoftICE directory in your search path.

Command Syntax
LOADER32 [[option(s)] filename]

Where options are:


Sounds cumbersome to me. Does not expedite things unless you device a way to do this "on the fly"

micmic
May 2nd, 2004, 09:38
Quote:
[Originally Posted by naides]Before you use LOADER32.EXE from a DOS prompt, use Symbol Loader's graphical interface to set the default search paths and to specify translation and debugging settings for each module you plan to load. Symbol Loader saves these settings for each file and uses them when you use Loader32 to load or translate files from a DOS prompt.

To run LOADER32.EXE, either set your directory to the directory that contains LOADER32.EXE or specify the SoftICE directory in your search path.

Command Syntax
LOADER32 [[option(s)] filename]


I've tried all these to no avail. Yes, both my app dir and SL directory where in the path and I specified directories and everything in SL, but still nothing.

I finally copied the Symbol Loader from SI 4.05 over the new one and it works again like a charm. Go figure...