btrieve for DOS single seat client under Windows 95

btrieve for DOS single seat client under Windows 95

Post by Doug Rowlan » Sat, 04 Apr 1998 04:00:00



Has anyone had any success getting Btrieve 6.15 for DOS single seat
(btrieve.exe) to work in a DOS box under Windows 95.  We are running the
DOS version of Magic version 5.70 and are having constant Illegal
Operations in Windows.  We can get it to run pretty well if we Restart
Windows in DOS mode.  But we still get pretty constant Error 3's.  I
don't understand this error.  These are stand-alone dos clients.  They
are not connected to a Btrieve server.

Thanks for any help,

Doug Rowland

 
 
 

btrieve for DOS single seat client under Windows 95

Post by Btrieve » Sun, 05 Apr 1998 04:00:00


A Btrieve status 3 indicates the file is not open. THe Btrieve for DOS will
work in Win95 DOS boxes. You jaust have to make sure that the application is
not a protected mode application as well.  Win95 doesn't support multiple
extenders in memory atthe same time.  Hope this helps.

 
 
 

btrieve for DOS single seat client under Windows 95

Post by Dennis Jacobs » Sun, 05 Apr 1998 04:00:00



Quote:>Has anyone had any success getting Btrieve 6.15 for DOS single seat
>(btrieve.exe) to work in a DOS box under Windows 95.  We are running the
>DOS version of Magic version 5.70 and are having constant Illegal
>Operations in Windows.  We can get it to run pretty well if we Restart
>Windows in DOS mode.  But we still get pretty constant Error 3's.  I
>don't understand this error.  These are stand-alone dos clients.  They
>are not connected to a Btrieve server.

Yes, we use it all the time under Windows 95 and it works fine.

Error 3 is file not open.  You can get this error if the file is
actually not open, but you are past that point.   We have had this
error if running low on RAM memory and then having the application
overwrite information in the Btrieve buffer.   If it gets conflicting
information, it thinks the file is closed, but really you have
corrupted the buffer.

Check the available RAM by using the MEM command in the DOS box under
Windows 95 and compare that run DOS directly.  I suspect you'll see a
difference.

Just for fun, check if the config.sys and autoexec.bat files load the
CD Rom drivers.   We have found that 75% of the computers installed
still have the DOS CD Rom drivers loaded after Windows 95 is
installed.  You can safely remove these, or at least remark them out,
as Win 95 will access the CD Rom.    This may give you some extra RAM.

Then again, I could be barking up the wrong tree.........

 
 
 

btrieve for DOS single seat client under Windows 95

Post by Steve Guido » Mon, 06 Apr 1998 05:00:00




>>Has anyone had any success getting Btrieve 6.15 for DOS single seat
>>(btrieve.exe) to work in a DOS box under Windows 95.  We are running the
>>DOS version of Magic version 5.70 and are having constant Illegal
>>Operations in Windows.  We can get it to run pretty well if we Restart
>>Windows in DOS mode.  But we still get pretty constant Error 3's.  I
>>don't understand this error.  These are stand-alone dos clients.  They
>>are not connected to a Btrieve server.

>Yes, we use it all the time under Windows 95 and it works fine.
>Check the available RAM by using the MEM command in the DOS box under
>Windows 95 and compare that run DOS directly.  I suspect you'll see a
>difference.
>Just for fun, check if the config.sys and autoexec.bat files load the
>CD Rom drivers.   We have found that 75% of the computers installed
>still have the DOS CD Rom drivers loaded after Windows 95 is
>installed.  You can safely remove these, or at least remark them out,
>as Win 95 will access the CD Rom.    This may give you some extra RAM.

I also have Btrieve DOS apps running under Win95 DOS boxes with no problems,
both stand-alone and networked.  When loading DOS Btrieve be sure to use the
/e parameter.  Also, what do you mean that your app works under straight DOS
'pretty well'?  You could have a bug in the app or its configuration that is
only being magnified by Win95.

Steve Guidos

 
 
 

btrieve for DOS single seat client under Windows 95

Post by Jaro » Tue, 07 Apr 1998 04:00:00


Simply is You must create a winstart.bat file in Windows directory, and
place a line to load btrieve.exe in this file. Btrieve must be run before
Windows is running.

Jaro




>>>Has anyone had any success getting Btrieve 6.15 for DOS single seat
>>>(btrieve.exe) to work in a DOS box under Windows 95.  We are running the
>>>DOS version of Magic version 5.70 and are having constant Illegal
>>>Operations in Windows.  We can get it to run pretty well if we Restart
>>>Windows in DOS mode.  But we still get pretty constant Error 3's.  I
>>>don't understand this error.  These are stand-alone dos clients.  They
>>>are not connected to a Btrieve server.

>>Yes, we use it all the time under Windows 95 and it works fine.
>>Check the available RAM by using the MEM command in the DOS box under
>>Windows 95 and compare that run DOS directly.  I suspect you'll see a
>>difference.
>>Just for fun, check if the config.sys and autoexec.bat files load the
>>CD Rom drivers.   We have found that 75% of the computers installed
>>still have the DOS CD Rom drivers loaded after Windows 95 is
>>installed.  You can safely remove these, or at least remark them out,
>>as Win 95 will access the CD Rom.    This may give you some extra RAM.

>I also have Btrieve DOS apps running under Win95 DOS boxes with no
problems,
>both stand-alone and networked.  When loading DOS Btrieve be sure to use
the
>/e parameter.  Also, what do you mean that your app works under straight
DOS
>'pretty well'?  You could have a bug in the app or its configuration that
is
>only being magnified by Win95.

>Steve Guidos

 
 
 

btrieve for DOS single seat client under Windows 95

Post by P Carvalh » Tue, 07 Apr 1998 04:00:00


Have you tried using Supportability?  It comes with the Single Seat Edition.

Supportability searches your system and registry looking for descrepancies.
Older Dlls, missing Dlls, etc...  Don't believe that the 6.15 install gives
you everything you need.

Btieve is nice enough to run without everything it needs.  It'll try to run,
but for the most part you'll wind up with mystery errors.

Good Luck


>Has anyone had any success getting Btrieve 6.15 for DOS single seat
>(btrieve.exe) to work in a DOS box under Windows 95.  We are running the
>DOS version of Magic version 5.70 and are having constant Illegal
>Operations in Windows.  We can get it to run pretty well if we Restart
>Windows in DOS mode.  But we still get pretty constant Error 3's.  I
>don't understand this error.  These are stand-alone dos clients.  They
>are not connected to a Btrieve server.

>Thanks for any help,

>Doug Rowland

 
 
 

1. Btrieve DOS under windows 95 with Client 32

Hello
We are trying to run a DOS program which uses Btrieve under Windows 95. It
uses Brequest. and the server is Netware 4.10 NDS
We are getting DOS error 7 and the Application just end or halt all the
system.
We tried all kinds of Batch files to run the requester, command.com, Norton
commander with Windows directory... .
Has anybody got a solution?
More then 12 milion records and a lot of people would appreciate
Lior Langer

2. Lookup Table Strangeness?

3. Error 96 when running 6+ user DOS/Novell application via Windows 95, Intraware 4.12, Btrieve 6.1

4. ODBC Outer Joins

5. Btrieve for DOS 5.10a and Windows 95 FAT32

6. Q: SQLDriverConnect (ODBC), VB4 &NT3.51

7. Btrieve Engine 6.15 für DOS, Windows, OS/2 oder Win NT/95

8. Unicode strings or escape sequence with sqlplus

9. bad performance: SPX, Netware, 4.10 + Btrieve 6.3, Windows 95 + Novell Client +MicroKernel32