[Dx4win] Re: DX4WIN and RigExpert Crashing System

[Anthony R Gargano N2SS]

That hotfix was for WINXP pre Service Pack 2. Service Pack 2 includes the 
fix and I am running XP with SP2.

My problem is still there. No problem to control the radio with DX4WIN 
through the RigExpert interface. If I set the Com port up for keying 
through DX4WIN I can send CW but I crash the computer when I use DX4WIN to 
either "Start" or "Stop" the radio. If I set up DX4WIN for LPT keying I do 
not have the crashing problem. So, there's definitely something DX4WIN 
doesn't like about this Com port setup.

I'm really scratching my head over this one. Anyone else have any thoughts? 
Thanks, Tony N2SS

At 04:02 AM 11/26/2005, you wrote:
>From: "M. Fitz" <mfitch at nbnet.nb.ca>
>Precedence: list
>Subject: [Dx4win] DX4WIN and RigExpert Crashing System ...
>Date: Fri, 25 Nov 2005 07:38:43 -0400
>To: <dx4win at mailman.qth.net>
>In-Reply-To: <20051125090131.D271E859FC1 at mailman.qth.net>
>Message-ID: <2005112573843.796188 at SEXDRIVE>
>Content-Type: text/plain; charset="us-ascii"
>MIME-Version: 1.0
>Message: 1
>
> >DX4WIN and RigExpert Crashing System ...
>
> >Message: 2  I am using DX4WIN version 7.01 in conjunction with a 
> RigExpert interface box.
> >I can get to the point of rig control and CW keying  and sending, but if 
> I click on Radio "Stop"
> >or Radio "Start" my  WinXP PC crashes and the Blue Screen indicates >the 
> file ks.sys as  the
> >culprit. I have tried various configuration set-ups both in  DX4WIN and 
> the RigExpert interface
> >box driver >but >always with the  same crashing problem. I had read 
> somewhere that DX4WIN
> >is not  friendly towards Com port CW keying. >Is >this my problem? Or am 
> I  missing something
> >in the configuration setups? Any suggestions  would be greatly 
> appreciated. >Thanks, Tony N2SS
>
>What kind of PC are using? I diid some looking around concerning ks.sys.
>There is a common blue screen error with ks.sys with Computers with
>Intel Hyper-Threading CPU. Microsoft is aware of this problem and created
>a hotfix, so you might check out the article and see if this fix might 
>help you?
>I've added the link below.
>http://support.microsoft.com/default.aspx?scid=kb;en-us;812035
>
>
>73 & GL Mark - ve9ts