Slicer.vxd

[AZScanner]

Anyone have the original source code to the slicer.vxd file that comes with Winflex? And anyone have any ideas how it could be recompiled to work with Windows XP?

Thanks,
-AZ

 

[remedy44]

Here is a newer copy of winflex

Admin Deleted: Yikes, please don't attach software that performs illegal functions!

 

[AZScanner]

Here is a newer copy of winflex

Still gives an error under Win2k: "Error loading Slicer.vxd".

But thanks anyway - you had me all excited for a minute there.

-AZ

 

[remedy44]

Not thinking straight sorry about that

 

[WayneH]

Rick can provide more info as I recall him talking about it but XP uses a different way of addressing/calling/whatever things so that VXD can't be used.

-Wayne

 

[SCPD]

AZ,

Use the WDM driver that comes with T4Win. It's small (5 kilobytes) and does the same thing. If you install it as a Windows Service, it's easier to work with than a serial port.

1. open file handle
2. issue IOCTL to select which pin(s) are to be monitored.
3. read data (lather, rinse, repeat).
4. close file handle.

Getting the SCM - Service Control Manager - to dynamically load and unload the driver is a PITA though.

I've got sample code showing how to use it. If you need the source code for the VXD, I've got that too but you will need a Windows 98 or newer DDK (device driver kit). It used to be a free download but now you have to register with M$ and order it on a CD.

-rick

 

[AZScanner]

AZ,

Use the WDM driver that comes with T4Win. It's small (5 kilobytes) and does the same thing. If you install it as a Windows Service, it's easier to work with than a serial port.

-rick

I'd love to see some sample code for using that. I've got the source code for POCFlex which would serve as a good test bed for experimentation. I really need to get off my butt and take a C++ course... damn VB - it's made me lazy. :lol:

Thanks for your help.
-AZ

 

[DaveNF2G]

Here is a newer copy of winflex

Admin Deleted: Yikes, please don't attach software that performs illegal functions!

I need to ask this Admin - what illegal functions?

There is nothing illegal about decoding the digital formats included in WinFlex. It is illegal to use that capability on certain frequencies. The software itself is perfectly OK.

 

[AZScanner]

There is nothing illegal about decoding the digital formats included in WinFlex. It is illegal to use that capability on certain frequencies. The software itself is perfectly OK.

Actually it isn't. Winflex (and POCFlex and PDW for that matter) infringe on Big M's Flex Patents, big time. That's why the author went into hiding and development exists now overseas only. But the slicer routines themselves are not protected under any patents and that's what I wanted help with.

I'm not the admin who took it down, but I understand why they did it.

-AZ

 

[SCPD]

I'd love to see some sample code for using that. I've got the source code for POCFlex which would serve as a good test bed for experimentation. I really need to get off my butt and take a C++ course... damn VB - it's made me lazy.

Well then use VB if you prefer. Do you know how to call "CreateFile" from VB ?

I'd have to create a ".INC" file to match the constants in the ".H" file used by C/C++. I'll throw together a "how to" article so folks can start using it.

-rick

 

[AZScanner]

Well then use VB if you prefer. Do you know how to call "CreateFile" from VB ?

I'd have to create a ".INC" file to match the constants in the ".H" file used by C/C++. I'll throw together a "how to" article so folks can start using it.

-rick

Oh yeah, Createfile from Kernel32, no problem there. Been playing with VB since 4.0 was the latest and greatest. Just starting fooling around with dot-net now, but it's a slow transition. I'm used to (and spoiled by) 6.0. I'd prefer to use VB since it's so easy, but most source code of interest (trunker, t4win, pocflex, etc) is all C and C++, so I really should stop being lazy and learn a "real language" to go with my knowledge of VB. I could then create/use DLL's written in C++ to do the majority of the dirty work so all the VB side has to do is put pretty windows on the screen.

I am looking forward to that article, that would be great for lazy people like me who use VB. Thanks!

-AZ