On Sun, Aug 20, 2006 at 12:26:34PM +0200, Niels S. Richthof enlightened us:
> > I think it is because of a typo in command lines, it should work now.
>
> I have absolutely no idea how this mistake could happen. I only used
> msparse.pl and replaced the "/?" with "/passive /n /norestart" after
>
Hi Eugene!
> I think it is because of a typo in command lines, it should work now.
I have absolutely no idea how this mistake could happen. I only used
msparse.pl and replaced the "/?" with "/passive /n /norestart" after
checking the command line options of each hotfix package.
Sorry for the m
Hi
Matt Hyclak wrote:
> > I tried retry a couple times with the same results - 246. When I chose
> > ignore, it was as you suspected - it continued and after the dust had
> > settled Automatic Updates wanted to install them.
> >
I think it is because of a typo in command lines, it should work now
On Sat, Aug 19, 2006 at 01:47:00PM +0200, Niels S. Richthof enlightened us:
> > After updating my cvs tree yesterday, I'm getting odd things happening on
> > about half a dozen XP SP2 updates. The update runs, but returns with code
> > 246,
>
> Ouch, that does not sound very good to me...
>
>
>
Hi Matt!
> After updating my cvs tree yesterday, I'm getting odd things happening on
> about half a dozen XP SP2 updates. The update runs, but returns with code
> 246,
Ouch, that does not sound very good to me...
> I'm in the process of searching for what return value 246 is, but thought
> I'd
After updating my cvs tree yesterday, I'm getting odd things happening on
about half a dozen XP SP2 updates. The update runs, but returns with code
246, so unattended doesn't know what to do and pauses waiting for
instruction - not terribly useful in an unattended setting :-)
I'm in the process of
