Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

DOS version of BTRIEVE on XP

Status
Not open for further replies.

sharder

MIS
Apr 3, 2001
22
CA
Does anyone have any success running an old DOS version of a BTRIEVE application on XP? By old, I'm talking circa 1993. MCSE-NT4.0, MCP-WIN2K
 
What version of Btrieve would you be referring to? It could be that even though the application is old the version of Btrieve doesn't have to be. I've found that some versions of Btrieve were not suitable for certain platforms.
 
I'm talking OLD. I can't even find a version number. The EXE is approx 100kb and dated 1987. MCSE-NT4.0, MCP-WIN2K
 
Yeah, that's pretty old. Do you have a BUTIL utility to go with that? If you do you should be able to do a BUTIL -VER to get the version number.
 
Even if you just run btrieve at the command line you should get a version number. I forgot to ask - is there a specific problem that you are having?
 
Wow,

It does my heart good to see that someone still uses Btrieve.

Years ago, my partner and I wrote a Multi User Medical Practice Management System using Btrieve (Was Softcraft back then) and (Wang) network.
This was back in 1987, Bill G did not have anything like that for years.

Move forward to the early 90's, Novell bought Btrieve and somewhat killed the after market for the product. Unfortunately, we had just developed a Btrieve based DOS Report Writer to compete with XTrieve. So, our market of developers dried up and we only sold several hundred copies. It was called Insight Report Writer.

I used Btrieve up through 4.15 on windows 98 platform.
We Used Btrieve and VB 2.0 until Bill finally got Access 2.0 working.

We also used our report writer internally (DOS Window) until 2001. This was again a Win 98 machine, but I would love to see if it would still go on a Win XP Box.

I may have some older btrieve info and programs on my shelf if you need them. I would have to dust off, because I ultimately went to Access and SQL, but old Bill did not get that right until almost 10 years after Softcraft, m-Dos, wang and Digital Recearch's C-Basic. Boy have I dated myself, but I just like to hear that somebody still uses Btrieve.

Have a Great Day,
Hap..

Access Add-on developer
 
The problem is twofold: it's as slow as molasses, and sucks CPU cycles like crazy. I seem to recall that we used to have to run some SHARE configuration options even to make this stuff work on a 286. Oh well, I much prefer Bill G anyway. MCSE-NT4.0, MCP-WIN2K
 
I agree, I use the tools that pay the bucks, so I love Bill's stuff.

but...
compared todays tools on a 2.4 gig 1 gig memory machine, now move back in time, what did bill have that would run on hardware 15 years ago... nothing.

And Btrieve, in 1985, would pull 50 records from a 200,000 table in 1 second on a 64 meg 8080 pc. And if you turned that power off mid stream, it recovered.

That is all I meant.

Later,
Hap Access Add-on developer
 
I also have developed using Btrieve from the Softcraft days, and continue to do so today utilizing the latest Pervasive versions. The last freely distributable DOS multi-user version was 5.10a which is about 43kb. My latest patch was from 1993. I have clients who still use DOS applications I've written using Btrieve.exe in a DOS box under Windows 98. Unfortunately, I've installed Pervasive SQL 2000i on all of my Workstations. The latest versions set up Win2k and WinXP to be "Btrieve ready" when opening a Dos Prompt or Command Prompt. I just tried executing Btrieve.exe in a DOS box and received the message "already loaded". A lot may still depend upon the application you are trying to run. Let us know what the application is. There is plenty of Btrieve and Pervasive help out here.
 
One of the reasons for it being slow might have something to do with the communications protocol. We found that when we switched to NT that we had to go the TCP/IP route rather than IPX/SPX because of the performance.
 
Yes. Explain the application and how it is started (i.e. batch file or executable). How are the calls to Btrieve made? We have been doing this for one of our older version of our application. Performance does not seem to be bad once you tweak the Novell client to work in this environment.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top