Board index » delphi » Interbase 6.0 and Windows ME: Serious performance problem on db open

Interbase 6.0 and Windows ME: Serious performance problem on db open

Here's an interesting one. We have a two-tier application that works fine
either standalone (client and IB server on the same machine)  or true client
server with client and server on separate machines.

It works fine on every combination but one of Win 95/98/ME and NT4/W2KK as
clients and servers (though I don't recommend to our clients to use Win 9x
as a server except in standalone mode, for obvious reasons.

The one combination that doesn't work well is if Windows ME is running the
server! Also, it's not our application per se, as the behaviour described
below happens in IBConsole.

What happens is that the first connection to the database takes an
inordinate time to happen ... about 30 to 40 seconds. Once that lag is
endured, subsequent connections are instantaneous, so it's happening in the
server. In IBConsole, opening the database happens quickly enough, but as
soon as I click on, say "Tables" (or "Domains" for that matter) I get the
30-40 second coffee-break opportunity. When developing at home that's
exactly what I do, open the database in IBConsole, then open Delphi. Once
open in IBConsole, I can go through the development cycle fine.

My machine at home is a PIII 800Mhz, 128Mb, tuned to the gills. I've tried
everything I can think of, including switching DMA on and off on the disks.

The behaviour described does not occur on a much less powered Win 98 test
box at work .. PII 450, 64Mb.

Unfortunately I've got a client who wants to run the app on Windows Me.

Any clues?

--

Regards, Stephen Walter

 

Re:Interbase 6.0 and Windows ME: Serious performance problem on db open


Quote
In article <3b609b15_1@dnews>, stephenwal...@optushome.com.au wrote...

Hi,

Quote
> Unfortunately I've got a client who wants to run the app on Windows Me.

ME has some sort of file journalling based on file extensions, one of
which is gdb.  Either give you database a different extension, or turn
the journalling off (not sure how though)

Cheers

Re:Interbase 6.0 and Windows ME: Serious performance problem on db open


According to MS support site, there is no way to disable it nor exclude GDB
extension from the protection list because the file witch contains that list
is also protected.

--
Sergio Samayoa
Lgica Software
http://www.geocities.com/logicasw/

Re:Interbase 6.0 and Windows ME: Serious performance problem on db open


If you look in  your (I think) readme.txt or install.txt, we have a work around
for this.

Quote
Sergio Samayoa wrote:
> According to MS support site, there is no way to disable it nor exclude GDB
> extension from the protection list because the file witch contains that list
> is also protected.

> --
> Sergio Samayoa
> Lgica Software
> http://www.geocities.com/logicasw/

--
Thank you,
Aaron Ruddick
InterBase QA
http://www.borland.com/interbase

Re:Interbase 6.0 and Windows ME: Serious performance problem on db open


I don't have those files. I use OS version.
Could be this file available to us whom don't have certified ?

--
Sergio Samayoa
Lgica Software
http://www.geocities.com/logicasw/

Re:Interbase 6.0 and Windows ME: Serious performance problem on db open


Protection from what?

--

Regards, Stephen Walter

Quote
"Sergio Samayoa" <serg...@terra.com.gt> wrote in message

news:3b60a3fa_2@dnews...
Quote
> According to MS support site, there is no way to disable it nor exclude
GDB
> extension from the protection list because the file witch contains that
list
> is also protected.

> --
> Sergio Samayoa
> Lgica Software
> http://www.geocities.com/logicasw/

Re:Interbase 6.0 and Windows ME: Serious performance problem on db open


From overwritting or deleting.

Useful links about system file protection (SFP):

http://www.microsoft.com/hwdev/sfp/WinME_sfp.htm
http://www.qbss.com/Zones/Delphi/DelphLines.asp?DelphLineNo=8

--
Sergio Samayoa
Lgica Software
http://www.geocities.com/logicasw/

Re:Interbase 6.0 and Windows ME: Serious performance problem on db open


Thanks for the info.

I just renamed the file to an extension other than .GDB, took the 30-40 sec
hit, which I now know is Windows ME taking a safety copy of my 250Mb
database. Then I opened the file in IBConsole and it came up straight away,
as it does in Windows 95/98.

Now to make my app open the file with its new extension, which is a mere
bagatelle.

--

Regards, Stephen Walter

Quote
"Sergio Samayoa" <serg...@terra.com.gt> wrote in message

news:3b60c5d0_2@dnews...
Quote
> From overwritting or deleting.

> Useful links about system file protection (SFP):

> http://www.microsoft.com/hwdev/sfp/WinME_sfp.htm
> http://www.qbss.com/Zones/Delphi/DelphLines.asp?DelphLineNo=8

> --
> Sergio Samayoa
> Lgica Software
> http://www.geocities.com/logicasw/

Re:Interbase 6.0 and Windows ME: Serious performance problem on db open


Jeff Overcash in borland.public.cppbuilder.database.interbaseexpress:

The file in question is the FileList.xml located in the
c:\windows\system\restore. Open it and remove the gdb entry in the includes
section and reboot. This should solve things. If it doesn't turn the System
Restore totally off.

Bruce

Re:Interbase 6.0 and Windows ME: Serious performance problem on db open


Quote
Sergio Samayoa wrote:

> I don't have those files. I use OS version.
> Could be this file available to us whom don't have certified ?

        Just search the newsgroups; Jeff Overcash posted all the options a
while ago.

        -Craig

--
Craig Stuntz (TeamB)       Senior Developer, Vertex Systems Corp.
Delphi/InterBase weblog:   http://delphi.weblogs.com
Use Borland servers; posts via others are not seen by TeamB.
For more info, see http://www.borland.com/newsgroups/genl_faqs.html

Re:Interbase 6.0 and Windows ME: Serious performance problem on db open


I tried editing FileList.XML, but as has been pointed out elsewhere in this
thread, FileList.xml is one of the files protected by this mechanism, so
editing it does nothing ... once you save it, protection kicks in and the
file is as it was before ... with GDB there in all it's glory.

This is a total PIA. I need a solution that I can incorporate in my
installations so that users who aren't into all the manual methods outlined
in this thread don't have to know about it .. it just gets fixed. The only
solution I can think of is to use another extension for my db, which is
do-able, but again a PIA as I have to reissue a fix for the client who has
Windows ME and make it backwardly compatible with the clients already
installed.

What in the name of God possessed Microsoft to add GDB to this file anyway.
I did a total search of my machine here at home and the only GDB files I
found were my databases and the demo databases that get installed with IB6.
Nothing whatsoever in c:\windows\ and below. Microsoft have no dependency on
these files and should have left it out.

--

Regards, Stephen Walter

Quote
"Bretislav Regner" <reg...@chemi.muni.cz> wrote in message

news:3b61358f_2@dnews...
Quote
> Jeff Overcash in borland.public.cppbuilder.database.interbaseexpress:

> The file in question is the FileList.xml located in the
> c:\windows\system\restore. Open it and remove the gdb entry in the
includes
> section and reboot. This should solve things. If it doesn't turn the
System
> Restore totally off.

> Bruce

Re:Interbase 6.0 and Windows ME: Serious performance problem on db open


According to MS you can't disable FPS. If you known how to disable, please
tell us.

--
Sergio Samayoa
Lgica Software
http://www.geocities.com/logicasw/

Re:Interbase 6.0 and Windows ME: Serious performance problem on db open


IMHO, WinME isn't exactly the best choice for a database server.  WinNT or
2000 are much better for this purpose.

--
Erik

Quote
"Sergio Samayoa" <serg...@terra.com.gt> wrote in message

news:3b64c72b_1@dnews...
Quote
> According to MS you can't disable FPS. If you known how to disable, please
> tell us.

> --
> Sergio Samayoa
> Lgica Software
> http://www.geocities.com/logicasw/

Re:Interbase 6.0 and Windows ME: Serious performance problem on db open


Totally agree with you but there is a pleny of small companies that just own
one computer and they just can't get another one with W2k just for running
one application.

--
Sergio Samayoa
Lgica Software
http://www.geocities.com/logicasw/

Other Threads