.

Classic PowerBASIC 9
  for Windows

Why upgrade to version 9?
Our classic GUI compiler for Windows. Need Premier Features?

Once priced $199...

    Now it's Just $99 !


Classic PowerBASIC 9 for Windows is a proven product with value pricing. It's a true professional compiler... Not too long ago, it was known as PowerBASIC 9.0 for Windows. Competitively priced at $199. But you can buy it today for just $99! What a great way to learn about PowerBASIC... it's a wonderful gift, an entry-level compiler, perfect for anyone who wants real value pricing.

Classic PowerBASIC for Windows is a native code compiler for all versions of Windows, from Windows 95 to Windows 7. It creates applications with a Graphical User Interface (GUI), to provide the typical "Look and Feel" of Windows. It creates highly efficient executables and industry-standard DLLs for optimum flexibility. The machine code generated by PowerBASIC is among the most efficient in the industry, both in terms of size and speed. It compares most favorably with leading compilers of any dialect, Pascal, C++, Fortran, and others. With PowerBASIC, you'll end BloatWare forever!

Classic PowerBASIC for Windows 9

This newest Classic version of PB/Win sports a number of exciting new features. Create client COM applications and COM components using Dispatch, Direct, Automation, or Dual interfaces. The inline assembler has been expanded to support the full range of SIMD opcodes. A complete graphics engine, a printer package for Windows-Only printers, dynamic pointers, and thread local storage, to name just a few. But more about them later.

Dynamic Dialog Tools™ (DDT™) allow you to create a complete graphical user interface with ease, using just built-in statements and functions. DDT is perfect for many applications, as it gives you complete access to all of the standard controls like menus, buttons, listboxes, text boxes, labels, bitmaps, listviews, treeviews, and much more. You can specify custom colors, custom fonts, and custom styles, for the Windows "Look and Feel", and best of all, your dialogs are truly dynamic! Controls can be modified, resized, moved, disabled, all under program control. Perhaps even more important, they're fast, fast, fast... loading as much as 20 times faster than Visual Basic forms. Try our complete SMTP email client, a 30k executable with a graphical user interface, that allows you to send an email message to anyone on the internet. Some other compilers can't display "Hello" in a program 40 times that size! Of course, for more complex user interfaces, you should probably consider PowerBASIC Forms, our state-of-the-art Visual Dialog Designer.

 
Total Cost Of Ownership


"I have been a PowerBASIC fan for years. I cannot imagine why anybody would use VB or .NET but I suppose it is all about marketing. Talk about the Total Cost Of Ownership!!!! One programmer and PowerBASIC can do what takes a room full of .NET folks to write and maintain."
    PowerBASIC has long been associated with performance. Our motto has always been smaller-faster, smaller-faster, smaller-faster. In fact, it's been said more than once that PowerBASIC is the "Consultant's Secret Weapon". So, how does it really stack up? In our comparisons, we've found that PowerBASIC can outperform Visual Basic by a factor from 3 to 23 times. That's correct, it's up to 2,300% faster than VB! Of course, PowerBASIC never requires any DLLs or run-times of any sort. So specifications on program size can be even more impressive. A "Hello, World!" program in VB is over 1,400,000 bytes with the necessary runtime code... but with Classic PowerBASIC Compiler for Windows? Just 5,632 bytes on disk, or 2,615 bytes in memory. That's something like 23,000% smaller than Visual Basic!

So just how fast is PB/WIN anyway? We thought you'd never ask! This tiny example may give you some idea of the power in PowerBASIC.

          x## = 1
          y## = 1.000001
          t! = Timer
          For i& = 1 To 100000000
              x## = x## * y##
          Next
          t! = Timer - t!
Which compiler should I choose?

What do we have here? 100,000,000 iterations of a simple floating point operation. On an AMD 64 CPU, PowerBASIC 3.5 for DOS runs this loop in 1.977 seconds. Pretty respectable, we think. PB3 has been benchmarked favorably against every sort of compiler... C++, Pascal, QuickBasic, you name it. It's always competitive.

So what about the Classic PowerBASIC for Windows? Same computer. Same operating system (WinXP Pro). Same source code, line for line. No attempt to minimize any background tasks. Elapsed time: 0.209 seconds. May we repeat that? Elapsed time: 0.209 seconds. That's an instant gain of around 945%! Windows versions of PowerBASIC are more than nine times faster than the best DOS Basic around!

PowerBASIC for Windows 9 IDE

So why the big difference? A number of reasons... Attention to detail. Attention to results. A philosophy that requires us to provide the very best possible code generation. We simply don't believe that sloppy coding can always be overcome by ever faster hardware. At some point, every programmer (ours included!) must take on the obligation to write quality code... and we take that obligation very seriously. That's why our entire compiler, including all the library code to be linked, occupies less than 265K! Compare that to multi-megabyte compilers that seem more like dinosaurs! That's a simple example of the attention we pay to careful programming.

Of course, performance is a factor of technical design issues, too. Like Register Variables. Normally, every time a variable is altered, assigned, or retrieved, memory must be accessed. That's a relatively slow process, as compared to accessing CPU and FPU registers. So PowerBASIC stores 4 float variables and 2 integer variables from each Sub/Function in a register instead of memory. Simple concept, but very effective. If those variables are referenced frequently, the improvement can be dramatic. Moreover, we let the programmer decide which variables should be register variables... that way, you can decide which will be most helpful. And if you still decline to choose, PowerBASIC will try to pick the best candidates for you, from those at hand.

PowerBASIC Clock Sample

So, how about graphics? Create a graphic control, open a graphic window, and you're ready to go! You'll use GRAPHIC PRINT to draw plain text or fancy text... Any font. Any size. Any color. Any escapement. Bold. Underline. Italic and strikeout. Mix any combination of fonts on any window. Print just about anything, just about anywhere, even on private bitmaps that aren't yet visible. You'll copy or stretch bitmaps. Shrink them or change them. Circles, ovals, lines and boxes. Fat lines, skinny lines, stylized lines. Arcs, circles, rounded rectangles. Ellipses, pie sections, polygons, polylines. Even get or set pixels -- one by one. Filled forms or empty. Colors or not. The choices are endless. You can mix new colors with those which exist, and measure proportional text size before you print it. Then create a custom scaling system, even with fractional floating point coordinates! Of course, once you've built that work of art, you need to load and save it: you'll load from a resource, load and save a BMP on disk!

And then there's printing. Access to printers has always been something of an issue, but not any more. First, we added the complete family of LPRINT functions, to give you direct text access to line printers. Then, we took it a step further with extended printing (XPRINT), even for "Windows-Only" printers! Just like GRAPHIC for the screen, XPRINT offers it all on the printer. Print plain text or fancy text -- any font, any size, any color. Bitmaps and images, lines and boxes, circles and polygons, virtually all the features of the GRAPHIC screen are there for printers, too! You can retrieve the size of the printer page, the printable area, the margins, even the number of points per inch. Select landscape or portrait mode, even the print quality setting. The PRINTER$() function returns the name and port of every available printer. You can attach a printer by its name, by default, or just display a printer dialog to let the user decide. It's all in there.

Another interesting point is that graphics are extensible. Using the DC (Device Context) from Classic PowerBASIC, you can call the Windows API, your own custom code, even third-party code for special graphic functions. With GRAPHIC GET/SET BITS, you can even manipulate the bitmap directly... each pixel is stored in succession as a long integer color value.

A complete Macro facility is an exciting addition to the latest version, and that's something seldom seen in a high level language. Essentially, a Macro invokes a text substitution engine which allows you to extend the PowerBASIC language in ways not seen before. PowerBASIC supports single line macros, multi-line macros, even function macros which return a result. And they don't occupy one byte of code space unless actually used. Each macro may take up to 240 arguments, so configurability shouldn't be an issue. MACROTEMP may even be used to specify identifiers which are made unique to each macro expansion, thus avoiding name conflicts. With PowerBASIC macros, you can design your own unique, personal language!

PowerBASIC is entirely thread-safe, so multi-threaded applications are a breeze. Isn't it good to know your program can handle 2, 3, or 5000 tasks, all at the same time? You can print a report, while still allowing data entry. Watch for a hardware signal, while calculating data services. All the power you need is packed right into the PowerBASIC Thread Statement, along with its simple extensions. Classic PowerBASIC even offers THREADED variables for "Thread Local Storage" -- each THREAD get its own unique copy of the variable -- automatically.

COM Components (Servers), create Dispatch, Direct, Dual, or Automation COM Components using easy to use built-in Basic like statements. Create classes with multiple interfaces, inheritance, constructors, destructors, private class methods, override inherited base classes, and much much more. Every object created or defined in PowerBASIC is fully compatible with the COM specification. Many popular compilers are not able to make that claim accurately. The COM specification defines a standardized method of communication between modules of code (frequently called components), regardless of the platform or the tool used to create them.

Client COM services, and support for the Dispatch, Direct, Automation, and Dual Interfaces lets you tap the power of components. Invoke libraries and applications with ease, all controlled from your Classic PowerBASIC client program. You'll find that the PowerBASIC object implementation is very efficient, with virtually no degradation of execution speed as compared to standard Subs and Functions. Invoke an instance of Microsoft Word, load and edit documents, all under the control of PowerBASIC? It's all there now, waiting for your command...

The Classic PowerBASIC IDE has had some major improvements. There's support for project files. Open multiple source code files from a single project file, even if the source files are saved in different locations. Further optimized debugging speed with improved reliability. The debugger also now support evaluation and modification of Field, Bit, and SBit variables. The IDE can insert a GUID (CTRL+ALT+G) which allows insertion of a unique GUID for COM and other operations. There's improved handeling of bookmarks and breakpoints. Printing from the IDE has been improved with margins and header with page, file information, date-time stamp and a separating line. All this, and even more, make the new IDE a joy to use.

Intuitive Code-Finder makes debugging easy

Extra debugging tools? Classic PowerBASIC shines with an array of built-in functions. PROFILE gives an overview. A list of every sub and function, how many times each was called, and the total time spent executing each of them. CALLSTK captures all stack frames above you. It answers, "How did I get here?". TRACE generates an execution log of each sub, function, label, and TRACE PRINT, as they're executed in sequence. It gives you parameter values, return values, even error codes. TRACE answers "Where have I been?", and "How did I get here?". With these tools, debugging might now be fun!

You know, a quality compiler must offer data types to suit the needs. And Classic PowerBASIC handles that with ease. Signed and unsigned integers to 64-bit. Single, double, and extended precision float. Two forms of currency. Dynamic strings, fixed strings, ASCIIZ strings. User-defined Types and Unions. Guids. Variants, pointers, and more. Now, we've added BIT and SIGNED BIT variables in TYPES and UNIONS. Each may be from 1 to 31 bits wide, packed one after another. Perfect for bit coding, or translation from C code. And FIELD variables? They work with the new FIELD statement, just like in DOS versions of BASIC. A FIELD is a string, mapped to a specific section of a file buffer, or even another string. They're allocated at run-time, so they can be changed as needed. Much like a TYPE that can be altered under program control. Best of all, a new internal design makes them fast, fast, fast!

Pointers are great, but sometimes the syntax is daunting, particularly for very simple tasks. So we implemented Dynamic Pointers, using the original PEEK/POKE as a model: xx# = PEEK(DOUBLE,addr&) This retrieves the double precision value stored at addr&, assigning it to xx#. Very straightforward and it works for all data types. And unlike the old PEEK and POKE, it's just as fast as a pointer variable! Speaking of simplification, LOCAL, STATIC, GLOBAL, and RESET can now use a list of variables, like: STATIC abc, bcd, xyz AS STRING And, ARRAY ASSIGN lets you assign values to every element of an array in a single statement!

At that, we're still not done. The Inline Assembler supports opcodes through Pentium class, including MMX. SIMD, and floating point. Built-in TCP and UDP functions allow you to download files from a web server, access an FTP site, send email over the internet, and even more. And Regular Expression Search and Replace offer amazing scan capabilities.

So simply put, one of our favorite slogans has been "We put the POWER in Basic..." We've said it before, but it's never been more true than it is today. With Classic PowerBASIC version 9, there's a renewed War On Bloatware! You know, using PowerBASIC for Windows, it's not unusual to deliver a substantial GUI application on a single floppy diskette. Don't let the Power of PowerBASIC pass you by...

New Features in Classic Version 9

  • #ALIGN metastatement aligns the next instruction to a boundary.
  • #COM DOC metastatement specifies a help string to be included in a COM Type Library.
  • #COM HELP metastatement specifies the name of the associated help file and the help context code to be included in a COM Type Library.
  • #COM NAME metastatement specifies the name of the server and the version number to be included in a COM Type Library.
  • #COM GUID metastatement specifies the GUID which identifies the entire application or library (APPID or LIBID) to be included in a COM Type Library.
  • #COM TLIB metastatment specifies that the compiler should create a type library for the compiled EXE or DLL.
  • #DEBUG CODE ON metastatement activates generation of debug code.
  • #DEBUG CODE OFF metastatement suppresses generation of debug code, from that line, until a subsequent #DEBUG CODE ON (or the end of the Sub/Function/Method/Property) is reached.
  • #DEBUG DISPLAY ON metastatement enables error display mode when an untrapped run-time error occurs within a compiled PowerBASIC program.
  • #DEBUG DISPLAY OFF metastatement suppresses displaying of untrapped error messages.
  • #INCLUDE ONCE metastatement includes a file only one time during compilation, regardless of how many times it appears in the program
  • #MESSAGES COMMAND metastatement specifies that only %WM_COMMAND messages are to be sent to a Controls Callback Function, just as in earlier versions of PowerBASIC.
  • #MESSAGES NOTIFY specifies that %WM_NOTIFY messages (as well as %WM_COMMAND messages) are to be sent to a Controls Callback Function.
  • #OPTIMIZE metastatement chooses between faster execution or smaller code size.
  • #UTILITY metastatement. Compiler directive to allow external utility programs to read text inserted on the #UTILITY line.
  • ACODE$ function may now contain an optional code page parameter. The code page parameter represents the code page to be used for the conversion process.
  • ARRAY SORT statement now offers a custom array sorting option. A custom array may be user-defined types, fixed-length strings, or ASCIIZ strings. With a custom array sort, you can write your own simple function to tell PowerBASIC the correct sequence for any two array elements.
  • ASM statement has been expanded to support the full range of SIMD opcodes. ASM statements may now contain a label - ASM Label: or ! Label:. Support for returning METHOD and PROPERTY return value assignments have been added.
  • BITSE function compares Integer class values for equivalent bits regardless of sign.
  • BGR function now accepts individual red, green, and blue values or a single RGB value.
  • BUILD$ function concatenates multiple strings with high efficiency.
  • Callback functions may now return a second result value through a special Windows data area named DWL_MSGRESULT.
  • CB.CTL function returns the control id for the message being processed in a Callback function.
  • CB.CTLMSG function returns the specific control message describing the event which occurred.
  • CB.HNDL function returns the window handle of the parent dialog in a Callback function.
  • CB.LPARAM function returns the wParam value for the message being processed in a Callback function.
  • CB.MSG function returns the numeric message value of the message being processed in a Callback function.
  • CB.WPARAM function returns the wParam value for the message being processed in a Callback function.
  • CB.NMCODE function returns the specific notification message describing the event which occurred.
  • CB.NMHDR function returns the address (a pointer) to the NMHDR UDT for a notification message.
  • CB.NMHDR$ function returns the contents of the NMHDR UDT as a dynamic string.
  • CB.NMHWND function returns the handle of the control which sent this message.
  • CB.NMID function returns the control id for the message being processed in a Callback function.
  • CLASS / END CLASS Block creates the code and data for an object.
  • CLIPBOARD GET ITEM statement retrieves a data item from the Windows ClipBoard.
  • CLIPBOARD GET TEXT statement retrieves a string from the Windows ClipBoard.
  • CLIPBOARD RESET statement deletes the contents of the Windows ClipBoard.
  • CLIPBOARD SET ITEM statement stores a new data item in the Windows ClipBoard.
  • CLIPBOARD SET TEXT statement stores a string in the Windows ClipBoard.
  • COMBOBOX FIND statement. Strings in the ComboBox are searched to find the first string which begins with the specified characters.
  • COMBOBOX FIND EXACT statement. Strings in the ComboBox are searched to find the first string which exactly matches the specified characters.
  • COMBOBOX GET COUNT statement returns the number of items in the ListBox of a ComboBox.
  • COMBOBOX GET SELCOUNT statement returns the number of selected items in the ListBox of a ComboBox.
  • COMBOBOX GET STATE statement checks to see if a specific item in selected.
  • COMBOBOX GET USER statement retrieves the value in the user data area of the ComboBox.
  • COMBOBOX INSERT statement inserts a new data item at a specific location.
  • COMBOBOX SET TEXT statement replaces a string for a specific data item with a new string.
  • COMBOBOX SET USER statement sets a value in the user data area of the ComboBox.
  • COMBOBOX UNSELECT statement sets all items in a ComboBox control to an unselected state.
  • COMM function has been enhanced to retrieve the Clear-To-Send (CTS) and Data-Set-Ready (DSR) states.
  • COMMAND$ function has been improved with an option to either return the complete trailer, or any one of the arguments.
  • CONTROL ADD LISTVIEW statement adds a ListView control to a dialog.
  • CONTROL ADD PROGRESSBAR statement adds a ProgressBar control to a dialog.
  • CONTROL ADD STATUSBAR statement adds a StatusBar control to a dialog.
  • CONTROL ADD TAB statement adds a Tab Control to a dialog.
  • CONTROL ADD TOOLBAR statement adds a ToolBar control to a dialog.
  • CONTROL ADD TREEVIEW statement adds a TreeView control to a dialog.
  • CONTROL SET FONT statement. Select a font to be used for a particular Windows Control.
  • DECLARE statements now support declarations of THREAD FUNCTIONS.
  • DIALOG FONT statement may now be used to specify the style and character set used for the dialog font.
  • DIR$ function has been expanded with an optional ONLY keyword to return only files that match the specified attribute. For example: DIR$(mask$, ONLY %SUBDIR ) just the directory entries which match mask$ are returned. The DIR$ function may optionally assign the complete directory data structure that receives information about the found file or subdirectory. to an appropriate UDT variable if you include the TO clause as a parameter.
  • DISPLAY BROWSE statement displays a folder selection dialog to return the user's choice.
  • DISPLAY COLOR statement displays a color selection dialog to return the user's choice.
  • DISPLAY FONT statement displays a font selection dialog to return user choices.
  • DISPLAY OPENFILE statement displays an OpenFile selection dialog to return user choices.
  • DISPLAY SAVEFILE statement displays a SaveFile selection dialog to return user choices.
  • EOF function now supports an optional # symbol preceding the file number parameter.
  • ERL$ function returns the last label, line number, or procedure name executed prior to the most recent error.
  • EVENTS statement attaches or detaches an event handler to/from an event source.
  • EXE.EXTN$ read-only user defined type returns the extension (with a leading period) of the program which is currently executing.
  • EXE.FULL$ read-only user defined type returns the complete drive, path, and file name of the program which is currently executing.
  • EXE.NAME$ read-only user defined returns just the file name of the program which is currently executing.
  • EXE.NAMEX$ read-only user defined returns the file name and the extension of the program which is currently executing.
  • EXE.PATH$ read-only user defined returns the complete drive and path of the program which is currently executing.
  • EXIT METHOD transfers program execution out of a METHOD structure.
  • EXIT PROPERTY transfers program execution out of a PRPOPERTY structure.
  • FIELD statement has been updated with two new options. FIELD STRING converts a field string to a dynamic string, assigns the current sub-section data to it. FIELD RESET converts a field string to a nul (zero-length) dynamic string.
  • FONT END statement destroys a font when it is no longer needed.
  • FONT NEW statement creates a new font for use with GRAPHIC PRINT, XPRINT, Controls, etc.
  • FOR/NEXT statements have been optimized. In certain situations, previous versions of PowerBASIC optimized FOR/NEXT loops to count down instead of up for improved execution speed. This optimization could cause the counter variable to contain a value which was not expected when execution of the loop was complete. This optimization has been improved so that the counter variable value is always correct upon loop completion, even if EXIT FOR was used to force an early termination.
  • FUNCTION/END FUNCTION statements may now be prepended with the word THREAD for clarity and self-documentation.
  • GLOBALMEM ALLOC statement allocates a moveable memory block.
  • GLOBALMEM FREE statement de-allocates a memory block.
  • GLOBALMEM LOCK statement lock a moveable memory block at a specific memory location.
  • GLOBALMEM SIZE statement returns the size of memory block.
  • GLOBALMEM UNLOCK statement unlocks a moveable memory block.
  • GRAPHIC BITMAP LOAD statement has been improved with an optional stretch mode parameter to enhance the quality of bitmaps which are changed in size.
  • GRAPHIC DETACH statement detaches a graphic target (Window, Control, or Bitmap) which may be currently attached to the process.
  • GRAPHIC FONT statement has been enhanced to allow the points and style attributes to be optional parameters.
  • GRAPHIC GET LINES statement retrieves the number of lines that can be printed on the graphic target.
  • GRAPHIC GET SCALE statement retrieves the current coordinate limits for the graphic target.
  • GRAPHIC IMAGELIST statement display an image from an Imagelist.
  • GRAPHIC INKEY$ statement reads a keyboard character if one is ready.
  • GRAPHIC INPUT statement reads data from the keyboard from within a Graphic Window.
  • GRAPHIC INPUT FLUSH statement removes all buffered keyboard data.
  • GRAPHIC INSTAT statement determines whether a keyboard character is ready.
  • GRAPHIC LINE INPUT statement reads an entire line from the keyboard from within a Graphic Window or a Graphic Control.
  • GRAPHIC SCALE PIXELS statement sets or resets the graphic coordinate system to pixel coordinates.
  • GRAPHIC SET FONT statement selects a font for the GRAPHIC PRINT, GRAPHIC INPUT, and GRAPHIC LINE INPUT statements.
  • GRAPHIC STRETCH statement has been improved with an optional stretch mode parameter to enhance the quality of resized bitmaps.
  • GRAPHIC WAITKEY$ statement reads a keyboard character, waiting until one is ready.
  • GRAPHIC WINDOW CLICK statement checks whether a GRAPHIC WINDOW has been clicked with the mouse.
  • IDISPINFO.CODE pseudo-object. When OBJRESULT is %DISP_E_EXCEPTION, this Get Property returns a long integer value which represents a more specific error code.
  • IDISPINFO.CONTEXT pseudo-object. When OBJRESULT is %DISP_E_EXCEPTION, this Get Property returns a long integer value which is the context of the topic within the help file (IDISPINFO.HELP$).
  • IDISPINFO.DESC$ pseudo-object. When OBJRESULT is %DISP_E_EXCEPTION, this Get Property returns a string containing a textual, human-readable description of the status.
  • IDISPINFO.HELP$ pseudo-object. When OBJRESULT is %DISP_E_EXCEPTION, this Get Property returns a string containing drive, path, and filename of a Help File with more information about this particular status code.
  • IDISPINFO.PARAM pseudo-object. When OBJRESULT is either %DISP_E_PARAMNOTFOUND or %DISP_E_TYPEMISMATCH, this Get Property returns a long integer value which represents the parameter number of the first parameter which failed to match the requirements needed.
  • IDISPINFO.SOURCE$ pseudo-object. When OBJRESULT is %DISP_E_EXCEPTION, this Get Property returns a string containing a textual, human-readable description of the source of the exception.
  • IDISPINFO.CLEAR pseudo-object. Clears all properties which may have been set by prior execution of IDISPINFO.SET in this thread.
  • IDISPINFO.SET pseudo-object. Sets the properties which for future execution of IDISPINFO.
  • IMAGELIST ADD BITMAP statement adds a memory bitmap to an ImageList.
  • IMAGELIST ADD BITMAP statement adds a resource or disk file bitmap to an ImageList.
  • IMAGELIST ADD ICON statement adds a memory icon to an ImageList.
  • IMAGELIST ADD ICON statement adds a resource or disk file icon to an ImageList.
  • IMAGELIST ADD MASKED statement adds a masked memory bitmap to an ImageList.
  • IMAGELIST ADD MASKED statement adds a masked resource or disk file bitmap to an ImageList.
  • IMAGELIST GET COUNT statement retrieves the number of images in an ImageList.
  • IMAGELIST KILL statement destroys a specified ImageList.
  • IMAGELIST NEW BITMAP statement creates a new bitmap ImageList.
  • IMAGELIST NEW ICON statement creates a new icon ImageList.
  • IMAGELIST SET OVERLAY statement declares an image in an ImageList as an overlay image.
  • INSTANCE statement declares an INSTANCE variable which is unique to each object.
  • INTERFACE / END INTERFACE Block (Direct) declares a direct object interface and its member Methods/Properties.
  • ISFILE function determines whether or not a file exists.
  • ISINTERFACE function determines whether an object supports a particular interface.
  • ISMISSING function determines whether an optional parameter was passed by the calling code.
  • ISWIN function determines whether a Control/Dialog/Window currently exists.
  • LET statement has been improved to support compound assignments (+=, -=, *=, /=. \=, &=, AND=, OR=, XOR=, EQV=, IMP=, and MOD=).
  • LISTBOX FIND statement. Strings in the ListBox are searched to find the first string which begins with the specified characters.
  • LISTBOX FIND EXACT statement. Strings in the ListBox are searched to find the first string which exactly matches the specified characters.
  • LISTBOX GET COUNT statement returns the number of items in the ListBox.
  • LISTBOX GET SELCOUNT statement returns the number of selected items in the ListBox.
  • LISTBOX GET SELECT statement searches the ListBox and returns the first selected item.
  • LISTBOX GET STATE statement checks an item in the ListBox to see if it is currently selected.
  • LISTBOX GET USER statement retrieves the value in the user data area of the ListBox.
  • LISTBOX INSERT statement inserts a new data item at a specified location in the ListBox.
  • LISTBOX SET TEXT statement replaces the string for a specific data item with a new string.
  • LISTBOX SET USER statement sets a value in the user data area of the ListBox.
  • LISTBOX UNSELECT statement sets a specific data item in the ListBox control to an unselected state.
  • LISTVIEW DELETE COLUMN statement deletes a column from a ListView control.
  • LISTVIEW DELETE ITEM statement deletes a data item from a ListView control.
  • LISTVIEW FIND statement. Strings in the ListView are searched to find the first string which begins with the specified characters.
  • LISTVIEW FIND EXACT statement. Strings in the ListView are searched to find the first string which exactly matches the specified characters
  • LISTVIEW FIT CONTENT statement adjusts the width of the specified column to fit the width of the data items displayed in that column.
  • LISTVIEW FIT HEADER statement adjusts the width of the specified column to fit the width of the data items displayed in that column, and the header text at the top of that column.
  • LISTVIEW GET COLUMN statement returns the width of the specified column.
  • LISTVIEW GET COUNT statement returns the number of data items in the ListView control.
  • LISTVIEW GET HEADER statement returns the specified column header text.
  • LISTVIEW GET MODE statement retrieves the display mode of the specified ListView control.
  • LISTVIEW GET SELCOUNT statement returns the number of selected items in the ListView control.
  • LISTVIEW GET STATE statement tests a data item to see if it is currently selected.
  • LISTVIEW GET STYLE statement retrieves the current setting of the ListView controls extended style.
  • LISTVIEW GET TEXT statement returns a string data item from the ListView control.
  • LISTVIEW GET USER statement retrieves the value in the user data area of the ListView control.
  • LISTVIEW INSERT COLUMN statement inserts a new vertical column in a Report Mode ListView control.
  • LISTVIEW INSERT ITEM statement inserts a new data item in the ListView control.
  • LISTVIEW RESET statement deletes all data items from the specified ListView control.
  • LISTVIEW SELECT statement the selects a specified string data item in the ListView control.
  • LISTVIEW SET COLUMN statement changes the width of a specific ListView column.
  • LISTVIEW SET HEADER statement sets the column header text to be displayed above the specified column on the ListView control.
  • LISTVIEW SET IMAGE statement displays the specified image next to the item specified.
  • LISTVIEW SET IMAGE2 statement displays a secondary "status" image next to the primary image.
  • LISTVIEW SET IMAGELIST statement attaches an Imagelist to the ListView control.
  • LISTVIEW SET MODE statement changes the display mode of the specified ListView control.
  • LISTVIEW SET OVERLAY statement displays the specified overlay image on top of the image specified.
  • LISTVIEW SET STYLE statement alters the current settings of the ListView controls extended style.
  • LISTVIEW SET TEXT statement replaces the text, if any, for the specified data item with new text.
  • LISTVIEW SET USER statement sets a value in the user data area of the ListView control.
  • LISTVIEW SORT statement sorts all the items in a ListView control.
  • LISTVIEW UNSELECT statement unselects a specified data item in a ListView control.
  • LISTVIEW VISIBLE statement. The specified data item is scrolled, if necessary, to ensure that the data item is visible.
  • ME pseudo-variable. A pseudo object variable to reference the current object.
  • METHOD / END METHOD statements defines a Method procedure within a class.
  • MYBASE pseudo-variable. A pseudo object variable to reference the inherited parent object.
  • OBJRESULT$ function returns a string which describes an OBJRESULT (hResult) code.
  • PATHNAME$ function parses a path/file name to extract its component parts.
  • PATHSCAN$ function finds a file on disk and returns the path and/or file name parts.
  • PRINT# statement, when used without any parameters outputs a blank line to the file (i.e. a CR/LF only).
  • PROCESS GET PRIORITY retrieves the Priority Value for the current process.
  • PROCESS SET PRIORITY sets the Priority Value for the current process.
  • PROGID$ function, has been enhanced to accept ProgIDs up to 99 characters, even though COM rules indicate that a ProgID cannot contain more than 39 characters.
  • PROGRESSBAR GET POS statement returns the current position of the ProgressBar.
  • PROGRESSBAR GET RANGE statement returns the current range of the ProgressBar.
  • PROGRESSBAR SET POS statement sets the current position of the ProgressBar.
  • PROGRESSBAR SET RANGE statement sets the minimum and maximum ranges of the ProgressBar.
  • PROGRESSBAR SET STEP statement specifies the default increment value to be used by the PROGRESSBAR STEP statement.
  • PROGRESSBAR STEP statement advances the current position of the ProgressBar by the default increment value.
  • PROPERTY GET statement retrieves a data value from an object.
  • PROPERTY SET statement assigns a data value to an object.
  • RAISEEVENT statement calls an Event Handler code.
  • RGB function now accepts individual red, green, and blue values or single BGR value.
  • SCROLLBAR GET PAGESIZE statement retrieves the current page size.
  • SCROLLBAR GET POS statement returns the current position of the ScrollBar.
  • SCROLLBAR GET RANGE statement Returns the current range of the ScrollBar.
  • SCROLLBAR GET TRACKPOS statement retrieves the current position of the scroll box.
  • SCROLLBAR SET PAGESIZE statement sets the current page size.
  • SCROLLBAR SET POS statement sets the current position of the ScrollBar.
  • SCROLLBAR SET RANGE statement sets the range of the ScrollBar.
  • SHELL statement now supports an optional EXIT TO clause. If specified, the exit code of the child process (the value returned by the WinMain function) is retrieved.
  • STATUSBAR SET PARTS statement sets the number of parts to be displayed in the StatusBar.
  • STATUSBAR SET TEXT statement assigns the text to be displayed in the specified part of the StatusBar.
  • TAB DELETE statement deletes a page from the Tab control.
  • TAB GET COUNT statement returns the number of pages in a Tab control.
  • TAB GET DIALOG statement retrieves the handle of the dialog for a specific page in a Tab control.
  • TAB GET SELECT statement returns the currently selected page in a Tab control.
  • TAB INSERT PAGE statement adds a new page to a Tab control.
  • TAB RESET statement deletes all pages in a Tab control.
  • TAB SELECT statement selects a specific page in a Tab control to be the active page.
  • TAB SET IMAGELIST statement assigns an ImageList to be used in a Tab control.
  • THREAD CREATE statement now supports an optional stack size parameter to specify the requested size of the stack for this newly created thread.
  • THREAD GET PRIORITY retrieves the Priority Value for a thread.
  • THREAD SET PRIORITY sets the Priority Value for a thread.
  • TIX statement measures elapsed CPU cycles.
  • TOOLBAR ADD BUTTON statement adds a button to a Toolbar control.
  • TOOLBAR ADD SEPARATOR statement adds a separator to a Toolbar control.
  • TOOLBAR DELETE BUTTON statement deletes a button from a Toolbar control.
  • TOOLBAR GET STATE statement retrieves the state of a button on a Toolbar control.
  • TOOLBAR GET COUNT statement retrieves the number of buttons on a Toolbar control.
  • TOOLBAR SET IMAGELIST statement attaches an ImageList to a Toolbar control.
  • TOOLBAR SET STATE statement sets the state of a button on a Toolbar control.
  • TREEVIEW DELETE statement deletes a data item from a TreeView control.
  • TREEVIEW GET BOLD statement retrieves the bold attribute for a data item.
  • TREEVIEW GET CHECK statement retrieves the checkmark attribute for a data item.
  • TREEVIEW GET CHILD statement returns the handle of the first child item of a specified data item.
  • TREEVIEW GET COUNT statement retrieves the number of data items in the TreeView.
  • TREEVIEW GET EXPANDED statement retrieves the expanded attribute for the data item.
  • TREEVIEW GET NEXT statement returns the handle of the next sibling data item.
  • TREEVIEW GET PARENT statement returns the handle of the parent for a specified data item is returned.
  • TREEVIEW GET PREVIOUS statement returns the handle of the previous sibling data item.
  • TREEVIEW GET ROOT statement returns the handle of the very first data item (topmost) in the TreeView.
  • TREEVIEW GET SELECT statement retrieves the handle of the currently selected data item.
  • TREEVIEW GET TEXT statement retrieves the text of a specific data item.
  • TREEVIEW GET USER statement retrieves the value in the user data area for a specific data item of the TreeView.
  • TREEVIEW INSERT ITEM statement adds a new data item to a TreeView control.
  • TREEVIEW RESET statement deletes all data items from the specified TreeView control.
  • TREEVIEW SELECT statement selects a specific data item in the TreeView control.
  • TREEVIEW SET BOLD statement sets the bold attribute for specific data item.
  • TREEVIEW SET CHECK statement sets the checkmark attribute for a specific data item.
  • TREEVIEW SET EXPANDED statement sets the expanded attribute for a specific data item.
  • TREEVIEW SET IMAGELIST statement attaches an ImageList to a TreeView control.
  • TREEVIEW SET TEXT statement replaces the text, if any, for the specified data item with new text.
  • TREEVIEW SET USER statement sets the value in the user data area for a specific data item in the TreeView control.
  • TREEVIEW UNSELECT statement sets all items in a TreeView control to an unselected state.
  • UCODE$ function may now contain an optional code page parameter. The code page parameter represents the code page to be used for the conversion process.
  • UCODEPAGE statement sets the default codepage used for ANSI / UNICODE conversions.
  • WINDOW GET ID statement returns the integer ID for a Window (usually a Control).
  • WINDOW GET PARENT statement retrieves the handle of the parent.
  • WRITE# statement, when used without any parameters outputs a blank line to the file (i.e. a CR/LF only). WRITE# has been extended to allow a trailing comma or semicolon, the final carriage return / line feed is suppressed and replaced with a comma delimiter.
  • XPRINT FONT statement has been enhanced to allow the points and style attributes to be optional parameters.
  • XPRINT GET COLLATE statement retrieves the XPRINT collate status.
  • XPRINT GET COLORMODE statement retrieves the XPRINT colormode status.
  • XPRINT GET COPIES statement retrieves the XPRINT copy count.
  • XPRINT GET DUPLEX statement retrieves the XPRINT duplex status.
  • XPRINT GET PAPER statement retrieves the current paper size/type.
  • XPRINT GET PAPERS statement retrieves a list of supported paper types.
  • XPRINT GET SCALE statement retrieves the current coordinate limits for the host printer page.
  • XPRINT GET TRAY statement retrieves the active printer tray.
  • XPRINT GET TRAYS statement retrieves a list of supported paper trays.
  • XPRINT IMAGELIST statement prints an image from an ImageList.
  • XPRINT SCALE PIXELS resets the coordinate system to the original default pixel coordinates.
  • XPRINT SET COLLATE statement changes the XPRINT collate status.
  • XPRINT SET COLORMODE statement changes the XPRINT colormode status.
  • XPRINT SET COPIES statement changes the XPRINT copy count.
  • XPRINT SET DUPLEX statement changes the XPRINT duplex status.
  • XPRINT SET FONT statement selects a font for the XPRINT statement.
  • XPRINT SET PAPER statement sets a new paper size/type.
  • XPRINT SET TRAY statement sets a new active printer tray.

Special features of Classic PowerBASIC for Windows

  • #STACK sets the program stack size
  • ACCEL ATTACH defines accelerators (shortcut hot-keys)
  • ACODE$() translates unicode strings to ansi
  • ARRAY SORT, SCAN, INSERT, DELETE
  • ARRAYATTR() returns status, data type, subscripts, etc.
  • ASCIIZ strings supported for Windows compatibility
  • Assembler is built-in for opcodes through Pentium class
  • BIN$() allows optional leading zeros to a fixed field size
  • BIT CALC set/reset a bit based upon a dynamic calculation
  • BIT SHIFT, ROTATE, TEST, SET, RESET and TOGGLE
  • BITS() function for bit pattern conversion between signed/unsigned
  • CALLSTK captures the entire stack frame
  • CHOOSE(index&, choice1, choice2...) chooses one of several values
  • CHR$() function may take multiple or a range of parameters
  • Client/Server Network communications using TCP and UDP
  • CLSID$(program_id$) returns the associated CLSID
  • Code pointer variables particularly suitable for callbacks
  • Compile to true machine code for maximum performance
  • Conditional compilation (#If/#ElseIf/#Else/#EndIf)
  • Create client COM applications and COM components using Dispatch, Direct, Automation, or Dual interfaces.
  • CSET centers data within a string with optional padding character
  • Currency variables with choice of two or four decimal digits
  • Data pointer variables with multiple levels of indirection
  • DDT (Dynamic Dialog Tools) builds complete GUI's
  • DECR statement for optimized execution
  • DISKFREE function returns the free space
  • DISKSIZE function returns the disk size
  • Extended-precision (80-bit) floating point variables
  • EXTRACT$() returns characters up to a delimiter
  • FILECOPY Statement supports overwrite of a previous version
  • FILENAME$() function returns the name of an open file
  • FLUSH statement ensures file data buffers are written to disk
  • FILESCAN obtains the number of strings in a file
  • FUNCNAME$ returns the name of the current Sub/Function
  • GUID variables are supported for COM Objects.
  • HEX$() allows optional leading zeros to a fixed field size
  • Huge file sizes greater than 2 Gigabytes are supported
  • IIF(expr, truepart, falsepart) returns one of two values
  • INCR statement for optimized execution
  • ISFALSE and ISTRUE operators
  • ITERATE statement restarts loop structures
  • JOIN$() packs a string array into a dynamic string
  • LINE INPUT #1, x$() reads an entire sequential file
  • MACRO defines a single-line, multi-line, or function Macro
  • MACROTEMP defines Temporary identifiers
  • MAT statement provides optimized Matrix operations
  • MAX() and MAX$() functions take an unlimited number of arguments
  • MIN() and MIN$() functions take an unlimited number of arguments
  • MOUSEPTR changes the mouse pointer to a new shape
  • OCT$() allows optional leading zeros to a fixed field size
  • PARSE$() function extracts a delimited field from a string
  • PARSE assigns each delimited string to an array element
  • PARSECOUNT returns the count of delimited fields in a string
  • PEEK/POKE, PEEK$/POKE$ for memory access
  • PRINT #1, x$() writes an entire array to a sequential file
  • PROFILE creates a complete profile of program execution
  • PUT #1,, x$() writes an entire array to a binary file
  • Quad-word 64-bit integer variables
  • READ$(n) function returns a specific DATA item
  • Register variables for both integer and floating point optimization
  • Regular Expression search and replace
  • REMAIN$() returns the remainder of a string after extraction
  • REMOVE$() returns a string with certain characters removed
  • REPEAT$() repeats an entire string expression
  • REPLACE statement replaces characters or expressions
  • RESET var sets a variable or array to zero or null
  • RND(x,y) returns a random integer between x and y
  • ROUND() function rounds a number to n decimal digits
  • Serial port communication is directly supported at all speeds
  • SETEOF statement sets the end-file position
  • Short-Circuit expression evaluation optimizes execution speed
  • STRDELETE$() deletes a portion of a string
  • String functions support ANY operator to operate on character basis
  • String functions support negative position to count from string end
  • STRINSERT$() inserts a string into another string
  • STRREVERSE$() reverses the character sequence in a string
  • SUB/FUNCTION may take up to 32 parameters
  • SWITCH(expr1, value1, expr2, value2...) returns one of a series
  • TAB$() expands tab characters to a specified tabstop
  • TALLY() counts the occurrences of a sub-string expression
  • Threads are supported as an intrinsic part of the language
  • THREADCOUNT returns the number of active threads
  • THREADID function returns the thread identifier
  • TRACE creates a trace log of complete program execution
  • TRY, CATCH, FINALLY, END TRY offers structured error handling
  • UCODE$() translates ansi strings to the unicode equivalent
  • User-Defined Types and Unions with optional alignment
  • Unsigned byte, word, and double word variables
  • USING$() function formats one or more expressions
  • Variant variables are supported for COM Objects.
  • VARIANTVT() returns the internal VT data type code
  • VERIFY() validates that all characters in string1 occur in string2
  • Win32 API may be easily accessed with no limitations

Minimum System Requirements

  • Personal computer with an 80386 or higher processor
  • Any version of Windows from Windows 95 through Windows 7
  • A hard disk with 13.0 Mb available space
  • CD-ROM or DVD drive, or Internet connection, for installations
Buy Now
Order Today   Read about our Satisfaction Guarantee

Classic PB/Win 9 is priced at $99. Registered owners of Classsic PB/Win 8 can upgrade to PB/Win 9 for $49, Delivery costs are additional. Click here for more information about upgrades.

Documentation for this product is provided in electronic form. An optional printed manual is available for $39 plus shipping.

See also...

. .