I am using the same system and could not get it to fail after several attempts.
de K8SIX At 01:16 AM 3/8/2007, ?ystein Stokkeland wrote: > >I could not create a crash the way described. I am using DXBase 2007, XP >Pro an 1 GB memory, on a 2.8MHz Intel CPU > > >73 de > >?ystein Stokkeland LA7QI >Tel: +47 51 67 70 97 / +47 971 56 090 >email: [EMAIL PROTECTED] > >*****Representant i Norge for DXbase logging program***** > > > >-----Original Message----- >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] >On Behalf Of Ed K1EP >Sent: 8. mars 2007 03:45 >To: Chris Codella, W2PA; 'DXBase List' >Subject: Re: [Dxbase] crash bug in DXB2007 > >Another data point. If I have the QSO toolbar that has the PrevQ icon on it >as a docked toolbar, it doesn't happen. If the QSO toolbar is NOT docked, >then it happens. Sure sounds strange to me. > >At 3/7/2007 09:34 PM, Chris Codella, W2PA wrote: > >Jack, John, and John, > > > >Thanks for checking. I agree it's a somewhat unusual sequence. I've been >using DXBase since 2000 and this is the first time I've hit it. > >But it's not completely outlandish either. Here's what I was trying to do: > > > >I searched for a particular DX QSO in the log, found it. The, on the spur >of the moment, I wanted to see all other QSOs with that same DXCC entity, so >I then clicked the prev-Q icon. Worked great! I finished what I wanted to >do with the information, closed the windows - boom. > > > >No harm done. > > > >73, > >Chris > > > >John W. Benedict wrote: > >>I was able to repeat just what Chris did using Win2K but it is not > >>something I would normally do. :-) > >> > >>John de KE5RS > >> > >> > >>-----Original Message----- > >>From: [EMAIL PROTECTED] > >>[mailto:[EMAIL PROTECTED] > >>On Behalf Of Jack > >>Sent: Wednesday, March 07, 2007 7:57 PM > >>To: Chris Codella, W2PA; DXBase List > >>Subject: Re: [Dxbase] crash bug in DXB2007 > >> > >>Chris, > >> > >>I don't see any crash here on our XP pro machine. But the simple answer >is don't do that! > >> > >>We will make a note of the issue and keep an eye open next time we are >into our portion of code involved. The "find" window is not actually our >code, but is MS, so if the issue is somehow triggered in that code, we would >need to solicit MS involvement as well. > >> > >>Cheers, > >>Jack > >> > >> > >> > > > >______________________________________________________________ > >Dxbase mailing list > >Home: http://mailman.qth.net/mailman/listinfo/dxbase > >Help: http://mailman.qth.net/mmfaq.htm > >Post: mailto:[email protected] > >______________________________________________________________ >Dxbase mailing list >Home: http://mailman.qth.net/mailman/listinfo/dxbase >Help: http://mailman.qth.net/mmfaq.htm >Post: mailto:[email protected] > >-- >No virus found in this incoming message. >Checked by AVG Free Edition. >Version: 7.5.446 / Virus Database: 268.18.7/713 - Release Date: 07.03.2007 >09:24 > > >-- >No virus found in this outgoing message. >Checked by AVG Free Edition. >Version: 7.5.446 / Virus Database: 268.18.7/713 - Release Date: 07.03.2007 >09:24 > > >______________________________________________________________ >Dxbase mailing list >Home: http://mailman.qth.net/mailman/listinfo/dxbase >Help: http://mailman.qth.net/mmfaq.htm >Post: mailto:[email protected]
