On Thu, 16 Aug 2007 08:36:30 -0000, Ali <abdulrazaq@gmail.com> wrote:>On Aug 16, 3:52 pm, The Real Andy <thereala...@nospam.com> wrote: >> On Thu, 16 Aug 2007 09:31:16 +0200, Leo Havm�ller >> >> <rtx...@nospam.nospam> wrote: >> >> That sounds like a useful testing tool. Where does it come from? >> >> >It comes from Mark Russinovich >> >(http://en.wikipedia.org/wiki/Mark_Russinovich). >> >You can download PortMon and many other useful tools from: >> >http://www.microsoft.com/technet/sysinternals/default.mspx >> >> >Leo Havm�ller. >> >> He wont go there, he hates MS. Mark and the other guy did a great job >> with all the SysInternals tools. I have been using their tools for >> years now. Hopefully they got enough cash from MS to retire on, cause >> they deserve it! > >Maybe, Its good for windows users. I hope M$ will replace their creepy >and * taskmanager with Mark's fine process explorer!Most of those tools reside permantly on my USB drive, especially process explorer. Really handy for nutting out those rouge processes on your brother-in-laws' computer!>Job does make us a good pet, I use to read Mark's explorations about >win* before he joined them, found always quite aggressive while >pointing the bug and malfunctioning. However, things are very >different now! > To feel the difference check this [ >http://www.microsoft.com/technet/technetmag/issues/2007/02/VistaKernel/ >] out , no he does sound like a sales person rather tech specialist.Microsoft does that to you, mind you, so do most big consulting, enterprise dev companies.>ali > > >
Anyone used Portmon on a USB-RS232?
Started by ●August 15, 2007
Reply by ●August 16, 20072007-08-16
Reply by ●August 16, 20072007-08-16
On 2007-08-16, Glyn Davies <sgd.work@googlemail.com> wrote:> CBFalconer wrote: > ><snip - questions about portmon serial monitoring> >> >> That sounds like a useful testing tool. Where does it come from? >> > > Come on - first hit on google > > Its one of the Sys-Internals tools, now owned by MicrosoftI'm unhappy to hear that sysinternals is now owned by microsoft. I assume the tools will be lobotomized and made useless now... -- Grant Edwards grante Yow! I want another at RE-WRITE on my CEASAR visi.com SALAD!!
Reply by ●August 16, 20072007-08-16
Grant Edwards wrote:> On 2007-08-16, Glyn Davies <sgd.work@googlemail.com> wrote: >> CBFalconer wrote: >> >> <snip - questions about portmon serial monitoring> >>> That sounds like a useful testing tool. Where does it come from? >>> >> Come on - first hit on google >> >> Its one of the Sys-Internals tools, now owned by Microsoft > > I'm unhappy to hear that sysinternals is now owned by > microsoft. I assume the tools will be lobotomized and made > useless now... >Had that pretty much confirmed recently :-( I needed some code to dig out a machines 'SID' - its unique identifier. Immediately thought of the old Sys Internals tool for changing your machines SID as a source of info. Tracked it down, only to find the source code download broken, and after a couple of emails that the 'source code is not available'. Don't blame them in a sense - they will have made a pretty penny out of it. Hope its not too long before someone else picks up their mantle. Glyn
Reply by ●August 16, 20072007-08-16
Ali wrote:> On Aug 16, 8:08 am, Joerg <notthisjoerg...@removethispacbell.net> > wrote: > >>Dirk Zabel wrote: >> >>>Joerg schrieb: >> >>>>Joerg wrote: >> >>>>>Ok, folks, Portmon shows COM6 which is the port to a scope, via a USB >>>>>connection. The terminal program (TeraTerm) is talking to it via that >>>>>port. Later it's going to be a VBA routine and that's why I need to >>>>>monitor, to see what gets stuck or doesn't appear. >> >>>>>Long story short I can set Portmon to monitor all other COM ports but >>>>>not COM6. Says "Portmon cannot attach .... device may be in use". >>>>>Well, duh, if it weren't in use I wouldn't need to monitor it ;-) >> >>>>>Is that normal? Any remedies? Use another port monitor software? Go >>>>>back to ye olde logic analyzer like I used to do it (it's heavy, >>>>>leads to backaches...)? >> >>>>Ok, found out a somewhat kludgy fix: Close the terminal program, start >>>>Portmon, then re-open the terminal. If Portmon isn't open and set to >>>>the desired COM port before the terminal program then Portmon won't >>>>work, at least not here. Strange, but at least it works now. >> >>>Hi Joerg, >>>in my experience that's normal behaviour with all programs which use the >>>com port. You have first to attach portmon to the port and than start >>>the program which generates the traffic I want to watch. >> >>Ok, thanks, Dirk. I didn't know that. It probably would be a good thing >>to mention in the troubleshooting section but I couldn't see anything >>about it there. >> >>Oh well, on to learning VBA then. Not that easy for an analog dude like >>myself, creating user forms and trying to make them control some >>hardware. That's why I need Portmon. >> >>-- >>Regards, Joerg >> >>http://www.analogconsultants.com > > > > > --snip-- > >>Oh well, on to learning VBA then. Not that easy for an analog dude like >>myself, creating user forms and trying to make them control some >>hardware. > > > Yeah, VB is most favorable for developing quick GUIs. But you might > give a try to C# from .net 2005, there is built in support for com > port and quite easy as compare to VB. >Well, I am quite cured of this .NET stuff. The scope's software needed it and I had to downgrade from 2.0 because there seems to be a serious lack of backwards compatibility in .NET. The file names were kept the same (!). No, not my cup of tea ;-) -- Regards, Joerg http://www.analogconsultants.com
Reply by ●August 16, 20072007-08-16
The Real Andy wrote:> On Thu, 16 Aug 2007 08:36:30 -0000, Ali <abdulrazaq@gmail.com> wrote: > > >>On Aug 16, 3:52 pm, The Real Andy <thereala...@nospam.com> wrote: >> >>>On Thu, 16 Aug 2007 09:31:16 +0200, Leo Havm�ller >>> >>><rtx...@nospam.nospam> wrote: >>> >>>>>That sounds like a useful testing tool. Where does it come from? >>> >>>>It comes from Mark Russinovich >>>>(http://en.wikipedia.org/wiki/Mark_Russinovich). >>>>You can download PortMon and many other useful tools from: >>>>http://www.microsoft.com/technet/sysinternals/default.mspx >>> >>>>Leo Havm�ller. >>> >>>He wont go there, he hates MS. Mark and the other guy did a great job >>>with all the SysInternals tools. I have been using their tools for >>>years now. Hopefully they got enough cash from MS to retire on, cause >>>they deserve it! >> >>Maybe, Its good for windows users. I hope M$ will replace their creepy >>and * taskmanager with Mark's fine process explorer! > > > Most of those tools reside permantly on my USB drive, especially > process explorer. Really handy for nutting out those rouge processes > on your brother-in-laws' computer! > > >>Job does make us a good pet, I use to read Mark's explorations about >>win* before he joined them, found always quite aggressive while >>pointing the bug and malfunctioning. However, things are very >>different now! >>To feel the difference check this [ >>http://www.microsoft.com/technet/technetmag/issues/2007/02/VistaKernel/ >>] out , no he does sound like a sales person rather tech specialist. > > > Microsoft does that to you, mind you, so do most big consulting, > enterprise dev companies. >Quote: "In Windows Vista most I/O operations can be canceled, ..." ^^^^ That begs the question, which ones can't be? As far as I am concerned if any machine that runs Windows out here doesn't have a reset button I find the place where I can connect one, drill a hole and mount a reset button. To make that convenient I've got a small parts bin of push buttons here with the correct diameter drill bit right in there :-; -- Regards, Joerg http://www.analogconsultants.com
Reply by ●August 16, 20072007-08-16
On Aug 16, 11:25 pm, Joerg <notthisjoerg...@removethispacbell.net> wrote:> Ali wrote: > > On Aug 16, 8:08 am, Joerg <notthisjoerg...@removethispacbell.net> > > wrote: > > >>Dirk Zabel wrote: > > >>>Joerg schrieb: > > >>>>Joerg wrote: > > >>>>>Ok, folks, Portmon shows COM6 which is the port to a scope, via a USB > >>>>>connection. The terminal program (TeraTerm) is talking to it via that > >>>>>port. Later it's going to be a VBA routine and that's why I need to > >>>>>monitor, to see what gets stuck or doesn't appear. > > >>>>>Long story short I can set Portmon to monitor all other COM ports but > >>>>>not COM6. Says "Portmon cannot attach .... device may be in use". > >>>>>Well, duh, if it weren't in use I wouldn't need to monitor it ;-) > > >>>>>Is that normal? Any remedies? Use another port monitor software? Go > >>>>>back to ye olde logic analyzer like I used to do it (it's heavy, > >>>>>leads to backaches...)? > > >>>>Ok, found out a somewhat kludgy fix: Close the terminal program, start > >>>>Portmon, then re-open the terminal. If Portmon isn't open and set to > >>>>the desired COM port before the terminal program then Portmon won't > >>>>work, at least not here. Strange, but at least it works now. > > >>>Hi Joerg, > >>>in my experience that's normal behaviour with all programs which use the > >>>com port. You have first to attach portmon to the port and than start > >>>the program which generates the traffic I want to watch. > > >>Ok, thanks, Dirk. I didn't know that. It probably would be a good thing > >>to mention in the troubleshooting section but I couldn't see anything > >>about it there. > > >>Oh well, on to learning VBA then. Not that easy for an analog dude like > >>myself, creating user forms and trying to make them control some > >>hardware. That's why I need Portmon. > > >>-- > >>Regards, Joerg > > >>http://www.analogconsultants.com > > > --snip-- > > >>Oh well, on to learning VBA then. Not that easy for an analog dude like > >>myself, creating user forms and trying to make them control some > >>hardware. > > > Yeah, VB is most favorable for developing quick GUIs. But you might > > give a try to C# from .net 2005, there is built in support for com > > port and quite easy as compare to VB. > > Well, I am quite cured of this .NET stuff. The scope's software needed > it and I had to downgrade from 2.0 because there seems to be a serious > lack of backwards compatibility in .NET. The file names were kept the > same (!). No, not my cup of tea ;-) > > -- > Regards, Joerg > > http://www.analogconsultants.comThats true, code written in .net 05 is not compatible with .net 05. ali
Reply by ●August 18, 20072007-08-18
Ali wrote:> On Aug 16, 11:25 pm, Joerg <notthisjoerg...@removethispacbell.net> > wrote: > >>Ali wrote: >> >>>On Aug 16, 8:08 am, Joerg <notthisjoerg...@removethispacbell.net> >>>wrote: >> >>>>Dirk Zabel wrote: >> >>>>>Joerg schrieb: >> >>>>>>Joerg wrote: >> >>>>>>>Ok, folks, Portmon shows COM6 which is the port to a scope, via a USB >>>>>>>connection. The terminal program (TeraTerm) is talking to it via that >>>>>>>port. Later it's going to be a VBA routine and that's why I need to >>>>>>>monitor, to see what gets stuck or doesn't appear. >> >>>>>>>Long story short I can set Portmon to monitor all other COM ports but >>>>>>>not COM6. Says "Portmon cannot attach .... device may be in use". >>>>>>>Well, duh, if it weren't in use I wouldn't need to monitor it ;-) >> >>>>>>>Is that normal? Any remedies? Use another port monitor software? Go >>>>>>>back to ye olde logic analyzer like I used to do it (it's heavy, >>>>>>>leads to backaches...)? >> >>>>>>Ok, found out a somewhat kludgy fix: Close the terminal program, start >>>>>>Portmon, then re-open the terminal. If Portmon isn't open and set to >>>>>>the desired COM port before the terminal program then Portmon won't >>>>>>work, at least not here. Strange, but at least it works now. >> >>>>>Hi Joerg, >>>>>in my experience that's normal behaviour with all programs which use the >>>>>com port. You have first to attach portmon to the port and than start >>>>>the program which generates the traffic I want to watch. >> >>>>Ok, thanks, Dirk. I didn't know that. It probably would be a good thing >>>>to mention in the troubleshooting section but I couldn't see anything >>>>about it there. >> >>>>Oh well, on to learning VBA then. Not that easy for an analog dude like >>>>myself, creating user forms and trying to make them control some >>>>hardware. That's why I need Portmon. >> >>>>-- >>>>Regards, Joerg >> >>>>http://www.analogconsultants.com >> >>>--snip-- >> >>>>Oh well, on to learning VBA then. Not that easy for an analog dude like >>>>myself, creating user forms and trying to make them control some >>>>hardware. >> >>>Yeah, VB is most favorable for developing quick GUIs. But you might >>>give a try to C# from .net 2005, there is built in support for com >>>port and quite easy as compare to VB. >> >>Well, I am quite cured of this .NET stuff. The scope's software needed >>it and I had to downgrade from 2.0 because there seems to be a serious >>lack of backwards compatibility in .NET. The file names were kept the >>same (!). No, not my cup of tea ;-) >> >>-- >>Regards, Joerg >> >>http://www.analogconsultants.com > > > Thats true, code written in .net 05 is not compatible with .net 05. >That's similar to what I've seen. Talking about version control ... As for me and my clients we'll rely on proven technology, where we know it works. -- Regards, Joerg http://www.analogconsultants.com
Reply by ●August 18, 20072007-08-18
On Sat, 18 Aug 2007 16:47:00 GMT, Joerg <notthisjoergsch@removethispacbell.net> wrote:>Ali wrote: > >> On Aug 16, 11:25 pm, Joerg <notthisjoerg...@removethispacbell.net> >> wrote: >> >>>Ali wrote: >>> >>>>On Aug 16, 8:08 am, Joerg <notthisjoerg...@removethispacbell.net> >>>>wrote: >>> >>>>>Dirk Zabel wrote: >>> >>>>>>Joerg schrieb: >>> >>>>>>>Joerg wrote: >>> >>>>>>>>Ok, folks, Portmon shows COM6 which is the port to a scope, via a USB >>>>>>>>connection. The terminal program (TeraTerm) is talking to it via that >>>>>>>>port. Later it's going to be a VBA routine and that's why I need to >>>>>>>>monitor, to see what gets stuck or doesn't appear. >>> >>>>>>>>Long story short I can set Portmon to monitor all other COM ports but >>>>>>>>not COM6. Says "Portmon cannot attach .... device may be in use". >>>>>>>>Well, duh, if it weren't in use I wouldn't need to monitor it ;-) >>> >>>>>>>>Is that normal? Any remedies? Use another port monitor software? Go >>>>>>>>back to ye olde logic analyzer like I used to do it (it's heavy, >>>>>>>>leads to backaches...)? >>> >>>>>>>Ok, found out a somewhat kludgy fix: Close the terminal program, start >>>>>>>Portmon, then re-open the terminal. If Portmon isn't open and set to >>>>>>>the desired COM port before the terminal program then Portmon won't >>>>>>>work, at least not here. Strange, but at least it works now. >>> >>>>>>Hi Joerg, >>>>>>in my experience that's normal behaviour with all programs which use the >>>>>>com port. You have first to attach portmon to the port and than start >>>>>>the program which generates the traffic I want to watch. >>> >>>>>Ok, thanks, Dirk. I didn't know that. It probably would be a good thing >>>>>to mention in the troubleshooting section but I couldn't see anything >>>>>about it there. >>> >>>>>Oh well, on to learning VBA then. Not that easy for an analog dude like >>>>>myself, creating user forms and trying to make them control some >>>>>hardware. That's why I need Portmon. >>> >>>>>-- >>>>>Regards, Joerg >>> >>>>>http://www.analogconsultants.com >>> >>>>--snip-- >>> >>>>>Oh well, on to learning VBA then. Not that easy for an analog dude like >>>>>myself, creating user forms and trying to make them control some >>>>>hardware. >>> >>>>Yeah, VB is most favorable for developing quick GUIs. But you might >>>>give a try to C# from .net 2005, there is built in support for com >>>>port and quite easy as compare to VB. >>> >>>Well, I am quite cured of this .NET stuff. The scope's software needed >>>it and I had to downgrade from 2.0 because there seems to be a serious >>>lack of backwards compatibility in .NET. The file names were kept the >>>same (!). No, not my cup of tea ;-) >>> >>>-- >>>Regards, Joerg >>> >>>http://www.analogconsultants.com >> >> >> Thats true, code written in .net 05 is not compatible with .net 05. >> > >That's similar to what I've seen. Talking about version control ... > >As for me and my clients we'll rely on proven technology, where we know >it works.I find that very hard to beleive. I have on my PC .net1.0, 1.1, 2.0, 3.0, 3.5 and they all work fine side by side. I have no problem with backward compatability. Furthermore, I have just finished writing a 1.1 app with VS2008. Works a treat.
Reply by ●August 19, 20072007-08-19
On Sat, 18 Aug 2007 16:47:00 GMT, Joerg <notthisjoergsch@removethispacbell.net> wrote:>Ali wrote: > >> On Aug 16, 11:25 pm, Joerg <notthisjoerg...@removethispacbell.net> >> wrote: >> >>>Ali wrote: >>> >>>>On Aug 16, 8:08 am, Joerg <notthisjoerg...@removethispacbell.net> >>>>wrote: >>> >>>>>Dirk Zabel wrote: >>> >>>>>>Joerg schrieb: >>> >>>>>>>Joerg wrote: >>> >>>>>>>>Ok, folks, Portmon shows COM6 which is the port to a scope, via a USB >>>>>>>>connection. The terminal program (TeraTerm) is talking to it via that >>>>>>>>port. Later it's going to be a VBA routine and that's why I need to >>>>>>>>monitor, to see what gets stuck or doesn't appear. >>> >>>>>>>>Long story short I can set Portmon to monitor all other COM ports but >>>>>>>>not COM6. Says "Portmon cannot attach .... device may be in use". >>>>>>>>Well, duh, if it weren't in use I wouldn't need to monitor it ;-) >>> >>>>>>>>Is that normal? Any remedies? Use another port monitor software? Go >>>>>>>>back to ye olde logic analyzer like I used to do it (it's heavy, >>>>>>>>leads to backaches...)? >>> >>>>>>>Ok, found out a somewhat kludgy fix: Close the terminal program, start >>>>>>>Portmon, then re-open the terminal. If Portmon isn't open and set to >>>>>>>the desired COM port before the terminal program then Portmon won't >>>>>>>work, at least not here. Strange, but at least it works now. >>> >>>>>>Hi Joerg, >>>>>>in my experience that's normal behaviour with all programs which use the >>>>>>com port. You have first to attach portmon to the port and than start >>>>>>the program which generates the traffic I want to watch. >>> >>>>>Ok, thanks, Dirk. I didn't know that. It probably would be a good thing >>>>>to mention in the troubleshooting section but I couldn't see anything >>>>>about it there. >>> >>>>>Oh well, on to learning VBA then. Not that easy for an analog dude like >>>>>myself, creating user forms and trying to make them control some >>>>>hardware. That's why I need Portmon. >>> >>>>>-- >>>>>Regards, Joerg >>> >>>>>http://www.analogconsultants.com >>> >>>>--snip-- >>> >>>>>Oh well, on to learning VBA then. Not that easy for an analog dude like >>>>>myself, creating user forms and trying to make them control some >>>>>hardware. >>> >>>>Yeah, VB is most favorable for developing quick GUIs. But you might >>>>give a try to C# from .net 2005, there is built in support for com >>>>port and quite easy as compare to VB. >>> >>>Well, I am quite cured of this .NET stuff. The scope's software needed >>>it and I had to downgrade from 2.0 because there seems to be a serious >>>lack of backwards compatibility in .NET. The file names were kept the >>>same (!). No, not my cup of tea ;-) >>> >>>-- >>>Regards, Joerg >>> >>>http://www.analogconsultants.com >> >> >> Thats true, code written in .net 05 is not compatible with .net 05.BTW: Please clarify what .net 05 is? If you mean the framework shipped with VS2005, then that would be .net 2.0>> > >That's similar to what I've seen. Talking about version control ... > >As for me and my clients we'll rely on proven technology, where we know >it works.
Reply by ●August 19, 20072007-08-19
On Thu, 16 Aug 2007 08:33:33 -0700, Joerg <notthisjoergsch@removethispacbell.net> wrote:>The Real Andy wrote: > >> On Thu, 16 Aug 2007 08:36:30 -0000, Ali <abdulrazaq@gmail.com> wrote: >> >> >>>On Aug 16, 3:52 pm, The Real Andy <thereala...@nospam.com> wrote: >>> >>>>On Thu, 16 Aug 2007 09:31:16 +0200, Leo Havm�ller >>>> >>>><rtx...@nospam.nospam> wrote: >>>> >>>>>>That sounds like a useful testing tool. Where does it come from? >>>> >>>>>It comes from Mark Russinovich >>>>>(http://en.wikipedia.org/wiki/Mark_Russinovich). >>>>>You can download PortMon and many other useful tools from: >>>>>http://www.microsoft.com/technet/sysinternals/default.mspx >>>> >>>>>Leo Havm�ller. >>>> >>>>He wont go there, he hates MS. Mark and the other guy did a great job >>>>with all the SysInternals tools. I have been using their tools for >>>>years now. Hopefully they got enough cash from MS to retire on, cause >>>>they deserve it! >>> >>>Maybe, Its good for windows users. I hope M$ will replace their creepy >>>and * taskmanager with Mark's fine process explorer! >> >> >> Most of those tools reside permantly on my USB drive, especially >> process explorer. Really handy for nutting out those rouge processes >> on your brother-in-laws' computer! >> >> >>>Job does make us a good pet, I use to read Mark's explorations about >>>win* before he joined them, found always quite aggressive while >>>pointing the bug and malfunctioning. However, things are very >>>different now! >>>To feel the difference check this [ >>>http://www.microsoft.com/technet/technetmag/issues/2007/02/VistaKernel/ >>>] out , no he does sound like a sales person rather tech specialist. >> >> >> Microsoft does that to you, mind you, so do most big consulting, >> enterprise dev companies. >> > >Quote: "In Windows Vista most I/O operations can be canceled, ..." > ^^^^ > >That begs the question, which ones can't be? As far as I am concerned if >any machine that runs Windows out here doesn't have a reset button I >find the place where I can connect one, drill a hole and mount a reset >button. To make that convenient I've got a small parts bin of push >buttons here with the correct diameter drill bit right in there :-;I would assume that critcal transactions such as writes to HDD (something that can cause corruption) cant be cancelled. I dare say this is probably transparent to most developers and would probably only concern kernal mode developers. As the article suggests "'In Windows Vista, device drivers easily register for notification of process terminations and so most of the un-killable process problems are gone."
