[Lazarus] Causing bluescreen on windows by move() procedure

[waldo kitty]

On 2/26/2011 14:24, Bo Berglund wrote:
> On Sat, 26 Feb 2011 19:29:48 +0100, Hans-Peter Diettrich
> <DrDiettrich1 at aol.com>  wrote:
>
>> Bo Berglund schrieb:
>>
>>> So it could be the Prolific USB-to-Serial driver then maybe?
>>
>> Very likely :-(
>>
>> BTW, is that a MS-certified driver?
> I think so, in fact Windows Update found a Prolific driver by itself.
> But it turned out to be real bad and then I searcehd the web and found
> a download on Prolific's website that solved all obvious problems I
> had with the prevcious one. So far it has worked seemingly perfect
> (until the BSOD that is).

that would seem to indicate that the driver code has not proliferated from the 
manufacturer to m$ or other OEM providers so that the old stuff is properly 
updated...

then, it appears that you might have found another bug that they may or may not 
know about ;)