Re: More metal installation troubles...

[fnet@randell.cba.csuohio.edu (Greg Boh)]

In article <Jq482B3w166w@hogbbs.scol.pa.us> lone@hogbbs.scol.pa.us (John Hale) writes:
>My installation works fine (yes, I even set up Metal.config right...) but 
>I crashes as soon as I get into the editor/programming environment, 
>with "Cannot execute module at $0000" or something of that ilk. I though 

Might want to try looking at how you have these options defined in your
config. Make sure that they do NOT have the .S extensions on them.

STARTUP=<program name>  This is the program that METAL will execute after
			it has crashed for some reason. Usually, it is the 
			1/STARTUP.S program for FV.

EXECMODULE=<program name> This is the program that METAL executes FIRST. It 
			  will only launch it once, at boot time. In FV 4, it
			  is the 1/PRECOMPILE.S ieb that will go through and
			  compile your 1/ directory. (All your IEBS.)

The error you described above may be caused by this.

If that doesn't work, then you have to take a look at your PATH statements..

PATH0=<*/>     		Where METAL will look for External Packg files.
			METAL.PACKG...
			...MAP
			METAL.OBJ1
			METAL.HELP...
			/COMMANDS
			COM.ALIAS

PATH1=<*/IEBS>		FutureVision Source Code directory     
PATH2=<*/SYSTEM>	FutureVision System Data Files
PATH3=<*/MENUS>		FutureVision Menu and Help files
PATH4=<*/NET>		FutureVision Network Files
PATH5=<*/USERS>		FutureVision Users Home and Mail directories
PATH6=<*/MESSAGES>	FutureVision Message Base files
PATH7=<*/LOGS>		FutureVision Logs
PATH8=<*/XFERS>		FutureVision Xfer files
PATH9=</CT3/WORKDIR>	METAL's "scratch" space. Put this on a fast device
			like /RAM5 and give it at least 256K to work with (For
			good measure)

>that maybe this was the default condition of not having a program in 
>memory, but whenever I do the restart option from the menu, it does the 
>same thing.

Actually, it is due to either the fact that METAL cannot FIND the file or that
the file does not exist. Look over your */METAL.CONFIG settings again and
match the, to what I have here.

> Also, it takes forever, (like, MUCH longer than proterm) to 
>init my modem. Would this have anything to do with the interrupt settings 
>that Proterm needs?? Thanks for any help -- I am looking for the techie 
>low-down on this fine dev pack.

Actually, it could do with the modem driver, some settings in your config etc
etc etc. Please refer to the file in your Documentation called 
CONFIG.COMMS for a detailed description of all the configuration options that
can be played with in the METAL.CONFIG file.

If you post a little bit more information about your Hardware (Modem type,
computer type, Flow Controlled??? etc...) We could help you a lot easier.