HP3000-L Archives

January 2001, Week 5

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Jeff Kell <[log in to unmask]>
Reply To:
Jeff Kell <[log in to unmask]>
Date:
Mon, 29 Jan 2001 18:45:49 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (29 lines)
Curt Brimacomb wrote:
>
> I an trying to setup network printing for a client, and I get an error I
> have never seen before after I had created the devices in ioconfig.  I was
> logged on as MANAGER.SYS at the time this happened. The error is:
>
> ioconfig:EXIT
>         keeping to group BOOTUP.SYS
>         Purge old configuration (yes/no)?Automatic yes
>         **error** can't purge configuration file MISCP.BOOTUP.SYS
>          SECURITY VIOLATION  (FSERR 93)

The last restart was NOT a start norecovery.  IOCONFIG can't save the
changes.  Your printers *are* however created and accessible, but only
for the duration of this boot.

As with all online configuration changes, the slightly undocumented
issue of saving the changes remains with IOCONFIG.

If you make the changes with SYSGEN and 'basegroup config' you can have
the changes saved to CONFIG.SYS (don't recall offhand if it will also
implement the changes online, I think it will).  This is much more
permanent, provided your *next* start is a start norecovery.

All in all, 'start recovery' (the default 'start') is getting less
useful and more dangerous in the long run.

Jeff Kell <[log in to unmask]>

ATOM RSS1 RSS2