SOZOBON users <<<<<HELP!>>>>>

SOZOBON users <<<<<HELP!>>>>>

Post by Chris L. Willis » Sun, 29 Aug 1993 04:38:24



Anyone-

This has got to be the dumbest problem in the world.  Check this out.

I have the following set-up:

- ATARI 1040STf       TOS 1.0  :-<
- 2 DS/DD Disk Drives

ok,

BOOT DISK:      

- AUTO/ETERNAL2.PRG
- AUTO/RAMDISK.DAT   w/  "D400"
- AUTO/((GEMENV.PRG - loads SOZOBON /BIN, /INCLUDE, /HOME, etc..)
   ROOT.ENV contains:
     LIB=A:\SOZOBON\LIB\
     INCLUDE=A:\SOZOBON\LIB\
     BIN=A:\SOZOBON\BIN\
     etc............
- VI (loaded into Ramdisk)
- .c source files (loaded into Ramdisk)
- MUPFEL.PRG & MUPFEL.MUP (loaded into Ramdisk)
   MUPFEL.MUP contains:
     PATH=A:\SOZOBON\LIB\;D:\
     CDPATH=D:\
     LIB=A:\SOZOBON\LIB;
     INCLUDE=A:\SOZOBON\INCLUDE\
     HOME=D:\
     etc..........

After the boot disk loads the gemvariables, creates a 400K ramdisk, and
copys all of the above programs to it, I replace it with a disk
containing:

    SOZOBON\BIN\
    SOZOBON\INCLUDE\
    SOZOBON\LIB\

right!  But wait.

when I am at the d:\ prompt, it WILL NOT RECOGNIZE ANY .TTP's THAT ARE
IN SOZOBON\BIN!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
so 'cc {filename}'  does NOT work --------- EVER!  :-<   :-<   :-<   :-<

my notorius MUPFEL 'PATH' should take care of that!
   PATH=a:\sozobon\bin\     right!!!!!!!!!!!!!!
(I have spent days changing the stupid gemenv variables, and saving them
to disk properly only to ovserve the save phenomenon -
                       'cc: does not exist'
I even tried adding the variables in GEMENV to the mupfel.mup variables,
in essence, copying the same paths verbatim and it still says duhhhhhh,
so and so 'does not exist' or something like that.

Quote:>>>>>>>>>>>>>>>>>>>>>>>>>>>>I don't want this stupid message anymore.

WHaat the heck is going on here?

Maybee I just have an incredibly STUPID shell.  Can someone recommend a
get-the-job-done, good-for-SOZOBON-C shell, or kindly offer a fix for
this system?  Is it my dumb TOS 1.0??

Thanks in advance.

Totally bewieldered.
--
( (  (   (    (     (      (       |       )      )     )    )   )  ) )

|                        "No Core Dump Required"                      |
( (  (   (    (     (      (       |       )      )     )    )   )  ) )

 
 
 

SOZOBON users <<<<<HELP!>>>>>

Post by Blair De » Thu, 02 Sep 1993 03:33:37



<Snip Snip>

Quote:>BOOT DISK:      

>- AUTO/ETERNAL2.PRG
>- AUTO/RAMDISK.DAT   w/  "D400"
>- AUTO/((GEMENV.PRG - loads SOZOBON /BIN, /INCLUDE, /HOME, etc..)
>   ROOT.ENV contains:
>     LIB=A:\SOZOBON\LIB\
>     INCLUDE=A:\SOZOBON\LIB\
>     BIN=A:\SOZOBON\BIN\
>     etc............
>- VI (loaded into Ramdisk)
>- .c source files (loaded into Ramdisk)
>- MUPFEL.PRG & MUPFEL.MUP (loaded into Ramdisk)
>   MUPFEL.MUP contains:
>     PATH=A:\SOZOBON\LIB\;D:\
>     CDPATH=D:\
>     LIB=A:\SOZOBON\LIB;
>     INCLUDE=A:\SOZOBON\INCLUDE\
>     HOME=D:\
>     etc..........

>After the boot disk loads the gemvariables, creates a 400K ramdisk, and
>copys all of the above programs to it, I replace it with a disk
>containing:

>    SOZOBON\BIN\
>    SOZOBON\INCLUDE\
>    SOZOBON\LIB\

>right!  But wait.

<Snip Snip>

Quote:>(I have spent days changing the stupid gemenv variables, and saving them
>to disk properly only to ovserve the save phenomenon -
>                       'cc: does not exist'
>I even tried adding the variables in GEMENV to the mupfel.mup variables,
>in essence, copying the same paths verbatim and it still says duhhhhhh,
>so and so 'does not exist' or something like that.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>I don't want this stupid message anymore.

Just a thought, but I don't see the SOZOBON\BIN\, SOZOBON\INCLUDE or
SOZOBON\LIB\ directories on your BOOT DISK.  When I installed Heat & Serve
C v1.4, I made my boot disk the program disk so it has all the sub-dirs &
prgs available when the paths are defined.  It doesn't seem likely, but TOS
may be checking for the existence of the sub-dirs & prgs when the variables
are being defined during boot.  If the sub-dirs aren't on the boot disk
they aren't defined properly and can't be found.

If they are on your boot disk, I wonder if their physical address is being
kept for reference later on.  If so, then the address TOS or your shell has
is no longer valid when the second disk goes in.

ps I'm using a single drive STe w/o a hard drive and I haven't had a
problem with Ian Lepore's Heat & Serve version of SOZOBON C.  Mind you I
don't get to play with it a lot.  BAD :)

Hope this helps  :)
--


         My opinion has been held over from previous life time.
------------------------------------------------------------------------

 
 
 

SOZOBON users <<<<<HELP!>>>>>

Post by John Trick » Fri, 03 Sep 1993 21:24:06




Quote:

> .....

>BOOT DISK:      

>- AUTO/ETERNAL2.PRG
>- AUTO/RAMDISK.DAT   w/  "D400"
>- AUTO/((GEMENV.PRG - loads SOZOBON /BIN, /INCLUDE, /HOME, etc..)
>   ROOT.ENV contains:
>     LIB=A:\SOZOBON\LIB\
>     INCLUDE=A:\SOZOBON\LIB\
>     BIN=A:\SOZOBON\BIN\
>     etc............
>- VI (loaded into Ramdisk)
>- .c source files (loaded into Ramdisk)
>- MUPFEL.PRG & MUPFEL.MUP (loaded into Ramdisk)
>   MUPFEL.MUP contains:
>     PATH=A:\SOZOBON\LIB\;D:\
>     CDPATH=D:\
>     LIB=A:\SOZOBON\LIB;
>     INCLUDE=A:\SOZOBON\INCLUDE\
>     HOME=D:\
>     etc..........

Chris, Look at the setting of PATH. Mupfel uses that to find its executables.
Now where is that typo, in this message or your file?

     PATH=A:\SOZOBON\BIN\;D:\

Just an idea.

John
--

       Voice: +44 21 524 8200     Fax: +44 21 553 6120

       +44 21 308 8892