On 17/09/11 20:22, Peter Coghlan wrote: It's all working nicely, but this is before an AUTOGEN. If I may I'll post the contents of the MODPARAMS.DAT and PARAMS.DAT to see if anyone recognises something bad. So, how did you get from where you were to where you are now? Have you recreated the system disk and got back to the point before you did the AUTOGEN? If so and you suspect AUTOGEN is going to mess things up again, then I suggest you record the system parameters before and after the AUTOGEN (AUTOGEN without the shutdown and reboot phases, that is) and compare them. Something like this: $ DEFINE /USER SYS$OUTPUT BEFORE.TXT $ MCR SYSGEN SHOW /ALL SHOW /SPECIAL ^Z $ $ @SYS$UPDATE:AUTOGEN SAVPARAMS SETPARAMS NOFEEDBACK $ $ DEFINE /USER SYS$OUTPUT AFTER.TXT $ MCR SYSGEN SHOW /ALL SHOW /SPECIAL ^Z $ $ DIFF BEFORE.TXT AFTER.TXT $ If everything looks ok, you can then reboot to get the new sysgen parameters take effect. If not, you have an opportunity to fix things before the shutdown and reboot makes things much more difficult to fix. Regards, Peter Coghlan. Hi Peter, I will do as you suggest. I have a disk in the box itself which is where the basis for the disk served by SLAVE comes from. So when I got to an unbootable state I have had to restore the disk. My good friend Malcolm suggested the following which is what worked with me without having to autogen: On 16/09/11 16:55, Malcolm Blunden wrote: Votes: Why do you run Autogen afterwards? A change of votes doesn't need any other change that I can think of. How are you changing the votes? Do you understand the arcane use of CURRENT and ACTIVE by SYSGEN? To set the votes to zero in a way that will apply at the next reboot, do $ MCR SYSGEN SYSGEN> USE CURRENT SYSGEN> SET VOTES 0 SYSGEN> WRITE CURRENT SYSGEN> ^Z That should fix it. Let me know if it doesn't work! - Malcolm.