Join Our Affiliate Program 
Sell our products and get paid immediately!

By promoting our award winning software on your website or your newseletter and earn some money.

By selling our products, your website can quickly be turned into a profitable online business.

Just sign up now and wait for our email (within 24 hours).

[ 1 comment ] ( 18 views )   |  [ 0 trackbacks ]   |  permalink  |  related link  |   ( 3 / 964 )
CheckListBox ActiveX version 2.6 SP5 is released 
A maintenance version of CheckListBox, Version 2.6 Service Pack 5, is released.

CheckListBox ActiveX Control provides support for listbox containing checkboxes, which is like the control that is built into Microsoft Word and Excel. In this control, each item's font, color, enabled and checked state can be individually modified. The control also supports 3D look, picture items and custom check mark. This package includes samples written in Visual Basic, Visual Basic .NET, Visual C#, Visual C++, Microsoft Access and Internet Explorer. CheckListBox is also called Check List.

In this version, WordWrap property is implemented. If WordWrap property is set to True, the control will automatically wraps words to the beginning of the next line when necessary. Following is snapshot of WordWrap sample.

FindString and FindStringExact methods are added, so you can easily search items in the listbox.

We also tested Visual Basic .NET, Visual C# and Visual C++ samples in Visual Studio 2005 Beta 2, and modified Prop sample and Color sample to make them compatible with this beta version.

Two small bugs are fixed:
  • Fix the bug that List Box appears without any border if the Appearance property set to claFlat(#10027).
  • Fix the bug that setting ListIndex will cause invalid property array index error in single selection mode(#10028).

    Please download full-feature evaluation version from

    Registered user can download the upgrade version from

    [ 1 comment ] ( 15 views )   |  [ 0 trackbacks ]   |  permalink  |  related link  |   ( 3 / 1214 )
    Vbio and Foxpro 
    I received a mail from Alberto O. Compagnucci. He told me his experience on VBIO and FoxPro. I want to share his idea with all our users. His mail is as follows:

    Dear Mr. Hai Li. I must thank you for vbio16.dll and vbio32.dll development, specially vbio16.dll because it is exactly what I was searching since a cop of months. I use Foxpro 2.6 Windows and I guess it is the only one Foxpro Windows (not Visual) 16 bits mode version and it's running in my PC under Windows 98. It runs under Windows 3.1 and Windows 95 too. Here is an example of how to use vbio16.dll with Foxpro 2.6 Windows. If you want, you can add it to others examples published in your Web page.

    Foxpro 2.6 Windows uses foxtools.fll special Foxpro library. It contains many functions but specially provides a special way to use external libraries. It is by using RegFn and CallFn functions. RegFn is to declare a external library function and CallFn executes it.

    Program example.

    SET LIBRARY TO SYS(2004)+"foxtools.fll" ADDITIVE

    **sys(2004) is a Foxpro System Function that provides the complete path to Foxpro directory.
    **ADDITIVE avoid others libraries to be disabled.

    inpuerto=RegFn("inport", "I", "I", "vbio16.dll")

    **This will return an integer to identify this declaration and wil be stored on the user memory variable "inpuerto".
    **"inport" is a vbio16.dll function to read a port.
    **First "I" is the parameter will be passed to the function, in this case it is port address as integer. Port address can be obtained from Windows 98 Pannel Control System Information or using DOS function DEBUG running Windows 98 in DOS mode. Some functions requires more than one parameter and the number of parameters required will be indicated with the same number of I. It is "II" or "III" and so on.
    **Second "I" specifies type of value will return RegFn. In this case it will be an integer. Foxpro will return zero for the first function declared, one for the second and so on; all of them stored at the desired user memory variable.
    **"vbio16.dll" is the library where Foxpro will search for the specified function.
    **You can declare all functions you want and Foxpro will return a handle integer for each one.
    **"Vbio16 function "inportw" can be declared in the same way.

    wpuerto=RegFn("outport", "II","I","vbio16.dll")

    **Same considerations listed for inpuerto but, note that in this case parameters to pass are two integers ("II"). First is port address, second is the byte to be written as integer.
    **"outportw" can be declared in the same way.

    readpuerto=CallFn(inpuerto, port address)

    **This will read a byte form the specified port and will be stored at "readpuerto" user memory variable.

    writepuerto=CallFn(wpuerto, port address, byte to be written as integer)

    **This will return the written byte as integer.


    **This releases all memory variables.

    RELEASE LIBRARY SYS(2004)+"foxtools.fll"

    **This releases "foxtools.fll" from memory.

    Reading about paralell port addresses is recommended.
    For further information about foxtools.fll using refer to an installed Foxpro 2.6; path C:\Fpw26\Goodies \Foxtools\foxtools.wri

    Congratulations Hai for your job. Special regards.

    Alberto O. Compagnucci

    [ 1 comment ] ( 372 views )   |  [ 0 trackbacks ]   |  permalink  |  related link  |   ( 3.1 / 384 )
    NTPort Library x64 Edition beta test 
    NTPort Library x64 Edition beta test starts.

    The x64 Edition supports AMD64 and Intel EM64T (IA32e) technology. The AMD Opteron™ processor, the AMD Athlon™ 64 processor, and AMD Turion™ 64 mobile technology comprise the AMD64 family.

    We supports both Windows XP Pro x64 and Windows Server 2003 x64. Under Windows x64 Edition, both 32-bit and 64-bit applications require 64-bit kernel drivers to access hardware devices. So even you are using 32-bit applications with NTPort Library, you still need x64 driver.

    In this beta version, fast mode is not supported yet. Because we use some undocumented kernel APIs in fast mode, and they are removed in Windows x64 Edition, so the fast mode is disabled in this beta test.

    If you are registered users of NTPort Library and interest in this beta test, please feel free to contact us.

    [ add comment ] ( 9 views )   |  [ 0 trackbacks ]   |  permalink  |  related link  |   ( 3 / 335 )
    64-bit ActiveX 
    Microsoft officially released Windows XP and Windows Server 2003 x64 edition. IE team introduced 64-bit browser in Windows x64 and recalled all vendors to write 64-bit ActiveX.

    We are trying to migrate our ActiveX controls to x64 platform(AMD64 and EM64T). Microsoft chose LLP64 data model, so that 32-bit ActiveX and 64-bit ActiveX can be compiled from same source code. Both 64-bit and 32-bit ActiveX can share same CLSID, because WOW64 presents 32-bit applications with an alternate view of the registry. Please notes Regsvr32.exe file in the System32 folder is a 64-bit version. When you run Regsvr32 to register a DLL, you are using the 64-bit version by default. If you want to register 32-bit version, please run Regsvr32.exe from the %SystemRoot%\Syswow64 folder.

    [ add comment ] ( 1 view )   |  [ 0 trackbacks ]   |  permalink  |  related link  |   ( 3 / 316 )
    Hotfix for Appearance property 
    We confirm there is a bug that the CheckListBox control appears to no border when Appearance property is set to claFlat. This bug was introduced in the last service pack. Registered users can request the hotfix via emails.

    A supported fix is now available from Zeal SoftStudio, but it is only intended to correct the problem described in this article. Only apply it to systems that are experiencing this specific problem. This fix may receive additional testing to further ensure product quality. Therefore, if you are not severely affected by this problem, Zeal SoftStudio recommends that you wait for the next service pack that contains this fix.

    [ add comment ] ( 3 views )   |  [ 0 trackbacks ]   |  permalink  |  related link  |   ( 3 / 3521 )
    Intel C/C++ compiler test 
    I attended the Intel Developer Forum(IDF) PRC Spring 2005 last week. I'm impressed by Intel C/C++ and Fortran compiler. I tried to test C/C++ compiler 8.1 with our flagship products, NTPort Library and MemAccess Library. 5 NTPort Library samples and 4 MemAccess Library samples are tested. Intel compiler has perfect compatibility with Microsoft Visual C++, all samples can run properly, but only two small issues of NTPort Library are reported in our test: warning #880 in Ntport.h and warning #1011 in FastMode sample.

    [ add comment ] ( 2 views )   |  [ 0 trackbacks ]   |  permalink  |  related link  |   ( 3 / 3130 )
    Warning #1011 
    I tested C/C++ compiler 8.1 with NTPort Library samples. Intel comiler reported following warning in FastMode sample:
    E:\Program Files\NTPort Library\VC\FastMode\FastModeDlg.cpp(190): warning #1011: missing return statement at end of non-void function "_Inp"

    If you want to disable this warning, please change _Inp function as follows:

    // Using inline assembler to increase performance further.
    // warning C4035: 'xxx' : no return value

    #pragma warning (disable:4035)
    BYTE _Inp(WORD Port)
    #pragma warning (default:4035)

    Here 4035 is the warning code of Visual C++, but Intel compiler also supports it. Wonderful!

    [ add comment ] ( 1 view )   |  [ 0 trackbacks ]   |  permalink  |  related link  |   ( 3 / 3056 )

    Back Next