I asked pre-sales tech support a number of questions, but they stated they do not have the knowledge needed to answer the questions. They suggested I post my questions here in hopes of a knowledgable reply.

Our customer currently has a database hosted by Btrieve V6.15 running on a NetWare V3.2 server. The clients run Integrated Accounting System software running on DOS computers and in DOS windows.

At this time, they would like to replace their server with a Windows Small Business Server 2003 R2 machine running PSQL V9. However, for various reasons, they want to keep their DOS clients.

The Pervasive website indicates PSQL V9 is file format compatible with Btrieve V6.15, so for the server side, can we simply move the database from the NetWare server to the Windows Server, install PSQL V9, and access the data without conversion?

The website also lists the client requiremetns for PSQL V9 as Windows 2000 or later. However, support documents on the website indicate that PSQL V9 supports various DOS requesters both on DOS machines and in DOS windows and that DOS applications should continue to work. Which is correct?

Can anyone offer any additional advice on whether this can work or not? Thanks for any help!

PSQLv9 still has native DOS support, unlike PSQLv10. However, native DOS support over TCP takes a lot of memory, so this solution MAY require the use of SPX for communications, similar to what you have today on NetWare.

The problem with TCP communications from DOS is that the MS client is SO freaking big, there's no memory left for the application on a DOS machine.

So, while the technical answer is YES, you can still run DOS clients, the more correct answer is NO -- you must upgrade if you intend to have a Windows SBS server.

However, if you want to play with it, you certainly can do so. Just note that this is a very difficult config to get working (I know -- I've tried several times with limited success), and you'll likely spend more time on the environment than it would cost to upgrade to newer hardware and newer OS.

If you do opt for this, then think about creating a hybrid client between the MS client and the Novell IPSODI stack, and then use SPX for communications. (SPX takes some xconsiderable effort to set up on the MS server, though.)

Of course, if you need on-site help, you now know who to call...

Bill:

Thank you for your reply. We did set up a test DOS client and noticed, as you stated, the footprint was big. I think there was about 114 KB left. So, we might consider the SPX approach.

Meanwhile, is it your feeling that using TCP/IP on a WXP client and running the DOS application in a DOS window should work?

Also, you didn't comment on the server side. Is it your feeling that we could simply move the V6.15 database from the NetWare server to the Windows Server, install PSQL V9, and access the data without conversion?

Thsnks!

Yes -- DOS applications on WinXP work wonderfully! I use lots of DOS apps myself, though I have just finished re-writing a number of them to Win32, since DOS apps will NOT run on a Vista64 box!

If your data is in thye Btrieve 6.x format, then just copy it over & go. If it is in the 5.x format (also supported by 6.15), then you'll have to rebuild it first, as PSQLv9 will NOT write to these files (and will return a Status 46 if you try).

Check the files with BUTIL -STAT, or look for any .PRE files while you're using it, and that'll be your clue that a rebuild will be needed.

Bill:

Just following up with our test results.  The Platinum for DOS accounting software was using Btrieve V6.15 on the NetWare V3.2 server.  We were able to simply copy the old application folder to the Windows Server 2003 system and access the database from PSQL V9.5.  We were also able to run the application from Windows XP client command prompt windows after increasing Files to 150 and Buffers to 45 in the Config.NT file.  We did identify Symantec AntiVirus Corporate Edition as a performance issue and had to disable it.  With SAVCE disabled, the application ran 5-10 times faster!  A huge gain.  After that, the application ran great.  The only exception we found was running the application in a DOS window via Terminal Services.  In that case, PFD caused a "NTDVM hard error" fault and halted.  All other DOS applications worked fine in that environment.  We have no clue as to the reason, but it's something we can live with.  Thanks for getting us started!

Tim

 This might help:

ERR - Error "NTVDM Encountered a Hard Error" When running a Win16 Application on Windows 2003 Server
Application:    Any Win16   
Version:    Any   
Platform:    Win2003 Server   
Engine:    PSQLv10   

Issue: (GS/DFE)
When attempting to run DFESoftware's Broker's Notebook on a PSQLv10 Server on Windows 2003 Server, we encountered an error immediately upon startup "NTVDM encountered a hard error" and the system fails immediately.

Resolution:
This is actually an issue with the Windows 2003 Server OS, the default TEMP file locations, and the Win16 application:

Try this work around solution: -
Select My Computer -> Properties -> Advanced -> Environment Variables -> User environment variable
Set TEMP and TMP to c:\temp
16 bit applications can't manage the spaces or long file names, and will generate ntvdm errors, even if they are not explicitly referencing the TEMP directory.