Darn power hiccups

[eaglescouter]

Good thing I was still up, otherwise I would have lost production all night due to a power hiccup. All of my machines shut down at the same time

I did not realize how long it takes to restart 6 machines when you have to swap KVM cables to get the job done.

 

[TC]

Can you set the bios option to restart on power loss and have seti driver in your startup folder? I'm fortunate enough to have a ups on most of my machines, but they're expensive.

 

[eaglescouter]

Can you set the bios option to restart on power loss and have seti driver in your startup folder? I'm fortunate enough to have a ups on most of my machines, but they're expensive.

That's a good idea which will help with a few of the machines.

The others are hindered by one or more of the following:
1. system halts because it cannot find the keyboard or mouse during the boot. Reason? I bought a cheap KVM switch and it has to be pointed at the machine during reboot or you get failures.

2. Some systems cannot find the keyboard/mouse because they don't have one. Cause? 4 position KVM switch with 3 sets of cables cannot service 5 machines.

3. Win2000 machines are set up with log-on passwords so they sit at that screen until the password is entered.

 

[ookabooka]

There should be an option in BIOS, like "halt on error" or something, if you disable it, it should boot up, even if it can't find a video card Should easily boot up without keyboard/mouse.

edit: about the win2000 login thing, couldn't u just run it as a service or add it into the registry somewhere to get it to run in the background?

 

[TC]

Yep that's a good point. If you install Seti as a service it doesn't need to be logged in to run. And your machines should be able to boot without keyboard and mouse cable connected if you select "halt on no errors."

 

[eaglescouter]

I did select stop on no errors in the bios, but the xp1700's wont finish the boot unless the keyboard and mouse are found.

I'll look at running seti as a service in Win2000, that sounds loke a great idea.

 

[gusgizmo]

or a better idea, since you cant connect to your queue when you are running it as a service and havent logged on yet is have the computer assume that a user is using it. i think this can be done by unchecking the "users must enter a . . . " setting in the users and passwords ocntrol panel. this is the best way to go. between that, and the bios settings, you could have a bullet proof system.

 

[TC]

If it's running as a service nobody needs to be logged on to connect to seti queue if you're using it. Services run all the time once the system is booted up.