10 seconds wouldn't cut it for me. I had to use a 20 second delay on dual
3.6GHz Xeons (although I didn't try 11-19). Maintainer: Would it be worth
adding a few more seconds onto this fix in perl.bat?
Thanks for this tip!
-
"Johnson, Chris A -ND" <[EMAIL PROTECTED]> writes:
> I only used a 10 second delay, and it worked like a charm.
I hate random delays. But since we do not even know what we are
waiting for, never mind how to wait for it from a cmd shell, I do not
see any choice.
I have added a 10-second delay to
> -Original Message-
> From: Patrick J. LoPresti [mailto:[EMAIL PROTECTED]
>
> The next step, I guess, is to add something like this to the top of
> perl.bat:
>
> ping -n 120 localhost > nul
>
I only used a 10 second delay, and it worked like a charm. Maybe I'll
try 5 seconds next t
"Johnson, Chris A -ND" <[EMAIL PROTECTED]> writes:
> So I'm still not sure whether it's time dependent or not. Very
> frustrating though!
The next step, I guess, is to add something like this to the top of
perl.bat:
ping -n 120 localhost > nul
This will sleep for two minutes before attempti
> -Original Message-
> From: Patrick J. LoPresti [mailto:[EMAIL PROTECTED]
>
> Maybe the service just takes a while to fire up the first
> time. Could you open a cmd prompt after the failure and run
> "z:\scripts\perl.bat"
> by hand?
In fact, the action of running a command prompt (Ct
Patrick J. LoPresti wrote:
"Johnson, Chris A -ND" <[EMAIL PROTECTED]> writes:
Let me know if you have any ideas, I know WS2K isn't on the
officially supported list, though.
We certainly aspire to support it. It is very, very similar to Win2k.
It has a few hotfixes unique to itself which we do no
"Johnson, Chris A -ND" <[EMAIL PROTECTED]> writes:
> Synopsis: Unattended installation using Windows 2000 Server goes
> great. Then it fails to complete the perl installation.
Hm. I have installed 2000 Server using Unattended before, but it has
been a while.
> It auto-logs on successfully (as
