It is not MY bug. Your implication is I am the only one who has seen it. I has happened to others... I don't know how many.
I do take exception to: "I don't know what to believe" & "SO-CALLED bug". Just what are you suggesting Guy? I spent many years as a developer, and my most recent position was as a Vice-President in charge of Information Technology for a large multinational. Technology has evolved since I was programming in the "Ancient Languages of Yore", but I do recognize a program bug when I see one... As I assume you know; some types of bugs are notoriously difficult to reproduce if they depend on random memory contents. I have also tried to reproduce it without success... it has only happened twice over a number of years so it's not a frequent occurrence. I have seen this bug twice on two different machines and two versions of D4W and there is unlikely anything wrong with my present computer as I have had it for years and use it extensively with both XP and Linux without any problems. I certainly don't have issues with data loss... and in any case, this bug does not involve IO. Mel... ON4AOI wrote: > Mel, > > I don´t know what to believe anymore, have been trying to reproduce > Your so called bug ? and gave up after 3 hours, nothing happened > The only way to get in demo mode is to start dx4win 2 times up, > Why you get this when using filters is a mistery , > Can be that your pc has a cash problem > Disable writeback of your hdd to eliminate possible data losses > > Why I have my doubts ? > It can be that my English is so poor on www.on4aoi.be concerning > Vista and Dx4win that it is not understandable for everybody (like to know > what to change) > but the following is from a mail you send only to me after I replied to the > reflector to read my tips. > MY STATEMENT = To start with admin privileges is only needed for the LPT > port driver and has nothing to do > With the serial port or driver , thought I explained it clearly on my pages. > > > This is your mail Mel > > Interesting... but not correct on my machine... a HP running Vista Home > Premium 64 bit. > Programs are installed in: C:\Program Files (x86)\dx4w707\ (the default) > I only needed admin privilege one time... to try to install the non-working > driver (gets rid of the message). > Now it appears to be running fine and doesn't require to be run with admin > privilege so doesn't generate UAC messages either. Caveat: I don't have the > serial communications set up on my Desktop... I only use it for manipulating > my log. > As XP has virtually disappeared on new machines... is Paul considering a > Vista (32/64) compatible driver, or is it too much trouble to write? > > > > GUY ON4AOI > > > MEL wrote: >>> I read those instructions and I don't entirely agree with them. >>> >>> You can install in the default location. >>> >>> You only need admin privilege to install the driver (which won't work >>> anyway... at least on my 64bit machine) >>> >>> Even if you did need admin privilege every time, the easiest way to run >>> it would be to click the "run as administrator" check box on the >>> "compatibility" tab of the shortcut used to launch DX4Win. > > MY ANSWER >> MEL, >> If you read the full instructions on my webpage how to start under Vista >> then you will understand it better. > >> -----Oorspronkelijk bericht----- >> Van: [email protected] [mailto:dx4win- >> [email protected]] Namens Mel >> Verzonden: vrijdag 8 mei 2009 19:03 >> Aan: DX4WIN >> Onderwerp: [Dx4win] The Demo Bug... Zapped again!!! >> >> It got me again... >> This time I was paying attention and made some observations... >> >> Though you can't save the log, you can filter and print it... so you >> can, at least, have a printout of recent activity... in my case it was >> just the last 2 QSOS. >> >> I did note that the bug strikes when using filters. I was confirming >> multiple QSOs for a station, so I was working with a small group of >> filtered QSOs and making multiple updates, one at a time using point >> and >> click. >> >> So I would suggest that you always do a save before working with >> filters >> until this is tracked down. >> >> For Paul... >> >> There is some kind of bug when working with filters. Perhaps it is >> related to the way I work... but I have run into errors when making >> multiple point and click changes followed by F10. Symptoms include: A >> record outside of the filtered set suddenly appearing in the list, F10 >> not stepping to the next record in sequence. I noticed this latter >> behaviour just before D4W lost track of the fact it is licensed. I was >> not able to reproduce the bug. I hope this helps in tracking it down... >> >> Mel, VE2DC >> ______________________________________________________________ >> Dx4win mailing list >> Home: http://mailman.qth.net/mailman/listinfo/dx4win >> Help: http://mailman.qth.net/mmfaq.htm >> Post: mailto:[email protected] >> >> This list hosted by: http://www.qsl.net >> Please help support this email list: http://www.qsl.net/donate.html > > ______________________________________________________________ Dx4win mailing list Home: http://mailman.qth.net/mailman/listinfo/dx4win Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[email protected] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
