Under DBISAM Ver 4.9, and Delphi 7, two of my clients running Client/Server
versions of my application have their system hanging under Windows 7.  The
time varies from when they start their computers to when the system freezes.

The system operates fine in Desktop mode.  I have Googled for help, and most
responses seem to indicate that the Registry needs cleaning.  The respondees
no doubt have ulterior motives, as one is then pointed to links to buy
registry cleanup software.

Both users have brand new computers, so it is unlikely they have already
both suffered from Registry problems.  I have played around with the Windows
firewall, for local users, and set the TCP Port, the Server and relevant
programs in the exceptions list but to no avail.

I've told them both to revert to Windows XP until I can resolve the issue.

Has any DBISAM user come across this problem so far, and if so how did you
overcome it?  Or is there some way to determine what is happening?

TIA.

Jim.

James


Nothing helpful but Sean McDermot has just reported a problem with Windows 7. He thinks its related to password protected files. Have a look in the dbisam.general newsgroup.

Roy Lambert

James,

Can you describe the setup a bit more - are you running the DBISAM server on
these machines (if yes then as a service or as a application) or is your
application simply acting as a client side of a client/server system with
dbisam server being on another machine/server ?

32 or 64 bit?

Anything in the event logs after the freeze?

Have you tried running your apps (and dbisam if local) as WinXP compatible ?

I've been using dbisam and win7 for 6+ months now with no problems. Most of
the win7 issues are usually related to permissions and file/folder/registry
redirection if you don't have a manifest.

I'd check drivers and AntiVirus first - those have been culprits for most of
the issues I've run into. Also VMWare and Foxit for some reason don't
co-exist well (issue is with Foxit so revert to old version if you use
vmware workstation and possibly player).

Finally - registry cleaning is unlikely the source of your problem. While it
can get corrupted (as any database) it's relatively rare. Removing info for
uninstalled apps, temp files, file associations and such is fine (but
unlikely to help you in this case) but if you want to try then CCleaner is
reasonably good (http://www.ccleaner.com/)

Raul





__________ Information from ESET NOD32 Antivirus, version of virus signature database 4720 (20091227) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

Hi Raul.

Slight correction to my initial post:  it is Version 4.29, not 4.9.

The Server is running as a Service.
Not sure if they are 32 or 64 bit.
I haven't used the event log before;  now that you mention it, I will have a
look and see what they contain.  I hope it doesn't get deleted upon
restarts.
I haven't tried to run under XP compatible mode, but that seems like
something to try out.
The users aren't using VMWare.

There are two slightly different scenarios with the two users:

User one has two new computers, each with Windows 7;  the Client running on
the same computer as the Server seems to go for a long time before it hangs;
the Client running on the other computer seems to run for only a few minutes
before it hangs and has to be restarted.

User number two has a new computer with Windows 7, on which the Server is
running;  the Client running on that computer seems to hang very soon after
it starts up;  two other computers both run Clients under Windows XP,
connected to the Windows 7 Server, and they have no problems at all.

I'm afraid I'm not up to speed with redirections and manifests, so don't
know what to do in that regard.  However, I'll look at registry/folder/file
permissions

What drivers should I check?

Thanks for your advice.

Jim.

"Raul" <raul@raul.ca> wrote in message
news:52A0B352-C91E-49DA-8D2B-2E00C2C1F1EC@news.elevatesoft.com...
> James,
>
> Can you describe the setup a bit more - are you running the DBISAM server
> on these machines (if yes then as a service or as a application) or is
> your application simply acting as a client side of a client/server system
> with dbisam server being on another machine/server ?
>
> 32 or 64 bit?
>
> Anything in the event logs after the freeze?
>
> Have you tried running your apps (and dbisam if local) as WinXP compatible
> ?
>
> I've been using dbisam and win7 for 6+ months now with no problems. Most
> of the win7 issues are usually related to permissions and
> file/folder/registry redirection if you don't have a manifest.
>
> I'd check drivers and AntiVirus first - those have been culprits for most
> of the issues I've run into. Also VMWare and Foxit for some reason don't
> co-exist well (issue is with Foxit so revert to old version if you use
> vmware workstation and possibly player).
>
> Finally - registry cleaning is unlikely the source of your problem. While
> it can get corrupted (as any database) it's relatively rare. Removing info
> for uninstalled apps, temp files, file associations and such is fine (but
> unlikely to help you in this case) but if you want to try then CCleaner is
> reasonably good (http://www.ccleaner.com/)
>
> Raul
>
> __________ Information from ESET NOD32 Antivirus, version of virus
> signature database 4720 (20091227) __________
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com

Hi Roy.

There must be a head wind across the Pacific, as I haven't seen Sean's post
as yet.  Hope I have the right group - elevatesoft.public.dbisam.general?

However, I'll take your advice and have a look at passwords in the systems.

Thanks again,

Jim.

"Roy Lambert" <roy.lambert@skynet.co.uk> wrote in message
news:3386C7C1-BFE2-48B3-90A7-08E068832344@news.elevatesoft.com...
> James
>
>
> Nothing helpful but Sean McDermot has just reported a problem with Windows
> 7. He thinks its related to password protected files. Have a look in the
> dbisam.general newsgroup.
>
> Roy Lambert
>

Hi Roy.

Further to my earlier reply, I have now come across Sean's post in the
dbisam.general group - it is under your Windows 7 topic of November 2.

Yes, I'm in the same boat as Sean:  the customers and techies think it's my
software at fault.  Guess a one-man show is heavily outnumbered by techies,
customers AND Microsoft.  Lucky we've got the dbisam newsgroups.

Regards,
Jim.

"Roy Lambert" <roy.lambert@skynet.co.uk> wrote in message
news:3386C7C1-BFE2-48B3-90A7-08E068832344@news.elevatesoft.com...
> James
>
>
> Nothing helpful but Sean McDermot has just reported a problem with Windows
> 7. He thinks its related to password protected files. Have a look in the
> dbisam.general newsgroup.
>
> Roy Lambert
>

James

Have you checked the policy to logoff clients automatically after 15 minutos
of inactivity ?

The names could be different because I am using Windows in Portuguese.

"Administrative Tools" / "Local security settings" / "Server settings: time
to disconnect sessions"

It could be the reason of the freeze.

Eduardo

Thank you Eduardo.

Another setting worth checking.  (However, it may not be this one, if set to
the default of 15 minutes).

Jim.

"Eduardo [HPro]" <contato@hpro.com.br> wrote in message
news:D820D953-38F1-4D33-BE85-7DECA8DD41BC@news.elevatesoft.com...
> James
>
> Have you checked the policy to logoff clients automatically after 15
> minutos of inactivity ?
>
> The names could be different because I am using Windows in Portuguese.
>
> "Administrative Tools" / "Local security settings" / "Server settings:
> time to disconnect sessions"
>
> It could be the reason of the freeze.
>
> Eduardo
>

James,

<< Under DBISAM Ver 4.9, and Delphi 7, two of my clients running
Client/Server versions of my application have their system hanging under
Windows 7.  The time varies from when they start their computers to when the
system freezes. >>

Is the whole computer freezing, or just your application ?

<< The system operates fine in Desktop mode. >>

What exactly do you mean by "Desktop mode" ?

Thanks,

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

Yes, the whole computer freezes.  Initially, the cursor has no effect on any
control, then about a minute later even the mouse freezes.  You can't
<Alt/Tab> to move around to other applications.

By Desktop mode, I mean embedded, where a single-user application does not
go through the Server, but is 'attached' to a Data folder directly below the
application ".\Data".

Regards,
Jim.