See comments inline below: On 6/21/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Thanks, all, for the help. And, some random responses to my many friends: > > > Hi Larry, I believe if you scroll down Phil's webpage, you will find > > a full set of instructions. The right vCom.sys is in the objckk > > subdirectory where you unzipped it. Phil gives instructions on how > > to change the COM port from 4/5 combo to anything you want. I > > believe he also shows how to hack the registry if you don't want to > > use the .ini file. > > de Ken N9VV > > > > There's ample and good instructions about changing the COM port numbers. > That much, I found. That does not (so far as I can tell) seem to be my > problem. > > COM4 and COM5 are fine choices. My system seems to stop at COM2. > > > When asked which driver to install you probably want the objfre one, it > > does not have the debugging stuff the checked one does > > > > And, how would I have known that? I don't remember seeing it on Phil's > web page. Or anywhere. I even tried reading the build logs, but the > differences were not obvious.
As Bill wrote earlier, it is explained in the entry for March 14, 2005: "You can choose to install either the checked build of the driver or the free build. Unless you know something about Kernel debugging the free build is the one you will want to install. The free build is in the folder objfre_wxp_x86\i386. The checked build is in the folder objchk_wxp_x86\i386. The driver file is called vcom.sys. When asked for the location of the driver file select Browse and go to the objfre_wxp_x86\i386 or objchk_wxp_x86\i386 folder and select vcom.sys." > I would be _ever_ so grateful if this install procedure were: > > 1. On its own web page. > > 2. In a readme file with the distro. > > 3. Put in an entry in the regular Flexradio forum. This is a nice > listserv, but some of the stuff needs to be, effectively, indexed. E-mail > is not the best for that. > > 4. All of the above. Are you volunteering? ;-) > I know, I know. This is a volunteer effort and all. The shoe may well be > on the other foot shortly, if I get my rear in gear and get some code > written (this is, in fact, prep for that). But, I was far more baffled > than I expected to be. The fact that it may _be_ me has occurred to me. > But still. . . As stated on the webpage, I still consider this driver to be alpha level code. It needs a lot of testing to be deemed acceptably stable. Build 114 is almost there. You use the driver at your own risk. Writing, testing, and debugging windows device drivers is nasty business and will make you old before your time. If you do not like BSODs, then please wait until it matures. Eventually documentation and a proper installation program will be written. Any volunteers? > Its just that I'm coming in the middle of the movie and I don't know the > plot. . . > > > After rebooting look in device manger, under multiple port serial > > adapters, > > it should show N8VB's vCom driver without any red or yellow decorations. > > > > Mine always had yellow decorations, whichever one I picked. :( If you are up for a little debugging, go to http://www.sysinternals.com/ and download DebugView. This handy little program will allow you to see kernel debugging messages from the driver's checked version. First, uninstall the driver in Device Manager and reboot. Start DebugView and then run the install.bat. When asked to select the driver, go to the objchk_wxp_x86\i386 folder and select vcom.sys. Debug messages should appear in DebugView telling where the installation failed. Post the messages here. > > Tell HRD to use one of the ports, tell SDR to use the other. > > And, how in the world would I have known to do _that_? I had them both on > COM4, which is what my intuition would have expected. The driver acts like a null modem cable. It connects two virtual com port pairs together like a real null modem cable. Maybe it should be renamed "Virtual Null Modem Cable" or something... > If I'm going to write my own code (the next step), do I just open the same > port as the one I'm giving Ham Radio Deluxe and ignore the existence of > the other one? > > > You need to > > be running one of my experimentals (1.3.5, 1.3.7) with the HRD fix, or > > need > > to be running Flex 1.3.8 -- 1.3.7 may work, I forget exactly which driver > > the HRD CAT fix went into. > > I think I'm running the right one. Yours/his at 1.3.5. > > Eventually, I expect to find out something embarassingly obvious that I > overlooked and this will all go away. But, if I can save the next poor > bloke, it will be worth it :) . > > I also noted in another posting that I should use something besides the > Kenwood T2000. I'm sure that's "hot off the presses" news, but it would > be nice if this sort of thing made its way into the sources above. . . This is not "hot off the press". It was also stated in the notes for May 26, 2005 on the webpage: " If you would like to try PowerSDR1.3.4 with HRD here is the binary and source changes. Copy the binary over the original PowerSDR.exe binary in the PowerSDR1.3.4 folder. In HRD select Kenwood TS-50S. " > Larry WO0Z > > PS, if it matters, I'm still on XP service pack 1. For a variety of > reasons, I can't upgrade to SP 2. Makes no difference... > _______________________________________________ > FlexRadio mailing list > [email protected] > http://mail.flex-radio.biz/mailman/listinfo/flexradio_flex-radio.biz > 73 de Phil N8VB
