From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <487A7FB0.7080009@proweb.co.uk>
Date: Sun, 13 Jul 2008 23:20:32 +0100
From: matt <mattmobile@proweb.co.uk>
User-Agent: Icedove 1.5.0.14pre (X11/20080304)
MIME-Version: 1.0
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
References: <81d62ec1df1079fe157c72cfa698435c@quanstro.net>
In-Reply-To: <81d62ec1df1079fe157c72cfa698435c@quanstro.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] Anatomy of a vblade image
Topicbox-Message-UUID: e49c97f6-ead3-11e9-9d60-3106f5b1d025

erik quanstrom wrote:
>> I'm serving drives to WinXP64 via AOE with http://winaoe.org/
>> I've had a few blue screens but I think they have been caused by the
>> server side serving bad data.
>>
>
> what do you mean by "server side"?
>
My dodgy programming :> I'm hacking around in vblade.c
Sorry, I see now I should have made that clear.


>
> it does sounds like the free windows aoe driver
> needs to handle the case where storage goes
> away more gracefully.  it may be that it is retransmitting
> too agressively.
>
>
I haven't had the ethernet sniffer looking at it


I got my data back btw. I ran the installer and guessed at what I'd told
fdisk :>