Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 10 of 19 total
Thread Error 8961, corrupt header...
Thu, Jun 22 2006 4:03 AMPermanent Link

ESKON a.s.
Hi I got problem with an error 8961 corupt header ...

Situation

1st app on W98SE, fills the dbisam table, located on win98
2nd app on WinXPP, reads the dbisam table located on win98
apps developed in D7, DBISAM 4.22-B3

If I run the first app which writes data into the table, then I can not run the secon app
because I got an 8961 error.
If I run both app on WinXP, on different machines everything is ok.
Also if I swap the apps on op. system like 1st(fills) app on WinXP, 2app(reads) app on
Win98, data on WinXP i do not get that error.


I went through the dbisam newsgroup and there is recomendation to use FlushBuffer method,
but also a notice that this is not 100%.
What should I do to prevent getting the 8961 error ? It has to be somehow related to the
Win98 I guess.

Thank you for help.

Michal Jiskra
ESKON a.s.
CZ
Thu, Jun 22 2006 9:38 AMPermanent Link

Michal Jiskra
I have modified our apps, using FlushBuffers methods but without any success. If I run 1st
app on W98 and then open table using DBSYS or our app on WinXP I get 8961 error.

Michal Jiskra
Thu, Jun 22 2006 9:58 AMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Michal


What happens if you repair the table, use the W98 machine to populate the the table, close the app on that machine and then open the app on WinXP?

Roy Lambert
Thu, Jun 22 2006 10:57 AMPermanent Link

"Erik"
A few years ago I had trouble with a peer-to-peer network with a Win98 and a
XP machine on some databasetables.
it came out that, if I had all tables on the xp machine, all went well,
but if I tried to access the tables on the Win98 machine via the network,
there was trouble (in some cases, not allways according to Murphy ! ).
finally we finded out it were tables with long-table-names which caused the
problems...

could that be the problem here too?


Erik


"Roy Lambert" <roy.lambert@skynet.co.uk> schreef in bericht
news:3797A63E-81CB-46B4-BFA5-D628DBDC18A3@news.elevatesoft.com...
> Michal
>
>
> What happens if you repair the table, use the W98 machine to populate the
> the table, close the app on that machine and then open the app on WinXP?
>
> Roy Lambert
>

Thu, Jun 22 2006 2:41 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Michal,

<< 1st app on W98SE, fills the dbisam table, located on win98
2nd app on WinXPP, reads the dbisam table located on win98
apps developed in D7, DBISAM 4.22-B3

If I run the first app which writes data into the table, then I can not run
the secon app because I got an 8961 error.
If I run both app on WinXP, on different machines everything is ok.
Also if I swap the apps on op. system like 1st(fills) app on WinXP,
2app(reads) app on Win98, data on WinXP i do not get that error. >>

What locale is the Windows 98 machine using ?  We are aware of some issues
with using the Turkish locale in terms of the way Windows 98 performs
collation vs. Windows XP.

--
Tim Young
Elevate Software
www.elevatesoft.com

Sat, Jun 24 2006 8:24 AMPermanent Link

Graham Wood
Similar problem with mixed clients when one or more had Win98SE.  Only solution is to get
them to bite the bullet and go all XP.  Trust me, you won't solve this.  MS knows about
it, and so do major accounting package vendors.  

Sorry the news couldn't be better.  The more time you invest without success, the less
likely the client will be happy to pay the invoice for your time, on top of the XP licenses.

Cheers,
Graham W.

Mon, Jun 26 2006 3:29 AMPermanent Link

Michal Jiskra
Hi Tim,
I am from the Czech republic, so the possible mutations of op. system could be English,
Czech.

We have not to repair the table, it is sufficient to stop the app running on W98 and I can
open the table from WinXP without any problems.

We do not use long names for the file-oriented database, so its "8.3" format.

Well I could try to create some example using table with english locale and then with
czech locale and we will see if the problem is in the locale setting.

Michal

P.S. Thanks to all.



"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote:

Michal,

<< 1st app on W98SE, fills the dbisam table, located on win98
2nd app on WinXPP, reads the dbisam table located on win98
apps developed in D7, DBISAM 4.22-B3

If I run the first app which writes data into the table, then I can not run
the secon app because I got an 8961 error.
If I run both app on WinXP, on different machines everything is ok.
Also if I swap the apps on op. system like 1st(fills) app on WinXP,
2app(reads) app on Win98, data on WinXP i do not get that error. >>

What locale is the Windows 98 machine using ?  We are aware of some issues
with using the Turkish locale in terms of the way Windows 98 performs
collation vs. Windows XP.

--
Tim Young
Elevate Software
www.elevatesoft.com

Mon, Jun 26 2006 1:26 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Graham,

<< Similar problem with mixed clients when one or more had Win98SE.  Only
solution is to get them to bite the bullet and go all XP.  Trust me, you
won't solve this.  MS knows about it, and so do major accounting package
vendors. >>

Do you have any links regarding this ?  I've never heard of any issues
mixing the two other than the normal Windows 95/98 network redirector
issues.

--
Tim Young
Elevate Software
www.elevatesoft.com

Mon, Jun 26 2006 1:36 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Michal,

<< I am from the Czech republic, so the possible mutations of op. system
could be English, Czech. >>

Okay, then that is probably not the issue.

I will have to look into this further.  I've done some quick Google searches
and can't come up with anything definitive.  There are some reports from
others that are having a similar problem with other file-sharing database
installations, but nobody seems to know what is causing it.  I suspect that
the SMB protocol in the two OS's has changed in some way that is preventing
proper operation.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tue, Jun 27 2006 6:47 AMPermanent Link

"Erik"
Hi,

Is there still any need to look at this, because Microsoft will stop support
on the older Windows versions (98, ME and NT) on july 11....

Erik


"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> schreef in bericht
news:D956D889-D1BC-420A-8B24-17DADE6321E9@news.elevatesoft.com...
> Graham,
>
> << Similar problem with mixed clients when one or more had Win98SE.  Only
> solution is to get them to bite the bullet and go all XP.  Trust me, you
> won't solve this.  MS knows about it, and so do major accounting package
> vendors. >>
>
> Do you have any links regarding this ?  I've never heard of any issues
> mixing the two other than the normal Windows 95/98 network redirector
> issues.
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com
>
>

Page 1 of 2Next Page »
Jump to Page:  1 2
Image