J
Jim Hurley
I have an application that runs fine on XP Pro machines but usually doesn't
work on XP Home. It doesn't crash or report any missing objects, it just
doesn't communicate well. Not sure what the exact problem is because some
parts work and some don't. No errors, just doesn't work. the program
communicates with a serial device and gets info back. Sometimes the info
comes back sometimes it doesn't appear to. On all the XP Pro machines it
works fine consistently. On the 3 XP Home machines we try it fails top work
the same on all 3 machines. The serial device works fine on XP Home using
the same C++ apps that wpork on the XP Pro boxes. It's just the .NET app
that has a problem. There is some wrapper code to implement the driver
dlls, but again this works fine on XP Pro.
The app does not use an security attributes, or security objects. It does
not check any file permissions or anything.
Any ideas?
jim
work on XP Home. It doesn't crash or report any missing objects, it just
doesn't communicate well. Not sure what the exact problem is because some
parts work and some don't. No errors, just doesn't work. the program
communicates with a serial device and gets info back. Sometimes the info
comes back sometimes it doesn't appear to. On all the XP Pro machines it
works fine consistently. On the 3 XP Home machines we try it fails top work
the same on all 3 machines. The serial device works fine on XP Home using
the same C++ apps that wpork on the XP Pro boxes. It's just the .NET app
that has a problem. There is some wrapper code to implement the driver
dlls, but again this works fine on XP Pro.
The app does not use an security attributes, or security objects. It does
not check any file permissions or anything.
Any ideas?
jim