So as everyone probably knew, it was a dodgy program. The two sub-forms were displayed using trhe ShowDialog method, and they were not setting a DialogResult as they closed themselves because I wasn't interested in how they exited.
But I am curious to know if anyone can shed light on why the fault only showed up on a single machine and not on all machines. It makes me wonder what other un-forced errors and ommissions there are in my code that have still to come out of the woodwork. In fact, how can I ever be sure that the code "wot I have wrote" is actually correct? Thoughts? ~A On Jun 16, 2:45 pm, Andrew <[email protected]> wrote: > Hi Guys > > I have a C# WinForms application that acts as a front end GUI to a Pic > based application. The systems talk via a USB serial port which looks > like COMx to the C# app. The PC's run XP Pro SP3 but the app runs ok > under Windows 7 on my development kit. > > The application is running well on several HP PC with Intel Core2 Duo > CPU's and runs well on several AMD X2 CPU's, all with XP Pro SP3. > > We recently bought aDellOptiPlex Core i5 machine and there are > several very strang happenings. > > With theDellrunning XP Pro SP3: > I have two custom Dialogue boxes that are one level below trhe main > application window, and when they are closed then the entoire > application just shuts down. I've traced it through and we just close > the sub-form, return to the button click event that invoked the sub- > form and then as we exit the click event the app calls the Dispose > event for the main form and we shut down the app. > > With theDellrunning Win7: > The above problem doesn't happen but I have a hit & miss connection > with the USB port. It always enumerates correctly when connected, but > trying to access will often produce a "Device has malfunctioned" error > message. This happens about once in three connections. > > With the HP's and other systems we have run on we see no problems at > all. > > TheDellperforms perfectly with all the other apps I've tried running > on it. > > I've tried disabeling the Hyperthreading, and also tried running it > down at a single core, but this has not affected the fault. > > Using VS2008 (I've tried using VS2010 as well but that didn't help > any) I can't trap any code between the exit from the click event that > instances the sub-form and the dispose that seems to signal the end of > the application. > > I have run out of ideas and so any input for other avenues to > investigate would be most welcome. > > Thanks. > ~A
