Lost ENV: ?
8 messages in this thread
What'd i do now?
I've been doing some restructuring of my disks when i suddenly find I can
no longer boot properly. Even my original Workbench floopy doesn't work,
only a combo of floppy KS and the Install disk allowed me to get this far.
From Power ON, I get a KS select screen with no HD options indicated. A
softboot at that time will not only find KS on SC0: but also begin the
startup script. It's going through standard CBM stuff and gets to
copy >NIL: ENVARC: ram:env all quiet noreq assign ENV: ram:env
and faults indicating it can't find ram:env
Switching over to floppies, i get up and SC0 looks fine
Currently I'm working with 2.03. I had similar problem yesterday with 2.01
and can't even get this far with copy of 2.04 i've got. Between 2.01 and
now, I was up and working as long as i kept a floppy (non booting) in one
of the drives (SC0: is on address 0 so timing is funny). I made mistake of
booting w/o floppy installed and all this started again.
machine is 3K little over a year old. Other SCSI disk/tape are not
bootable.
Anyone have any ideas and/or able to give me some info on ENVARC:? lGlamb
Change the startup to create the directory RAM:ENV before it does
the copy of ENVARC:
Don
Thanx. Noticed that and found it was changed in 2.04 scripts. I'm now
using ROMs for assorted reasons. But I still can't understand how it was
working for some time. Can RAM: structures carry over reboots (power
offs)?
Facintaing. The copy should have worked, eeven without the makedir. The ALL
keyword will create the directory if none exists.
-larry
Larry,
Nope…RAM: can't even survive a warm start let alone a power
off/on cycle.
Don
hmmmm, let me wrap back to my first question then, what/where exactly is
this ENVARC: assigned? I had been playing with the disk partitions on that
disk and had one partition named SC0 I believe. My 'local' shop had
reports that the various 2.x soft kickstarts were having problems with
other than the standard 3 partition disks? After installing the ROMs
everything seems to be fine.
BTW did anyone post a clarification to the CBM ROM install note? They say
to removed the ROM tower then continue. There should be clarification that
you replace chips in the tower and reinstall entire assembly. Fortunately
the shop went through this confusion before me.
By default, ENVARC: is assigned to SYS:prefs/Env-Archives. It's
assigned automatically, much like C: is…however, I don't think the
assignment "takes" until it's first reference since in my case, I boot from
a floppy (the original sys:) and then re-assign it to my hard drive and
then refernece envarc: and it shows up properly as being on the hard drive,
not the floppy.
That would be equivalent to the DEFER option to ASSIGN, where the
assignment doesn't really take place until it's first usage.
Still can't figure how that could explain the sometimes work sometimes
don't but i'm certainly not gonna take the machine apart to investigate it
now that i'm up again.
Thanx for info. lGlamb