I had replied to the comment of:
Did not you see vdos here?
This works fine now!
(but it only went to guus and not the group)
So I am going to start a whole new question:
We are running Netware 6.5 on a WAN, 5 locations and about 25 users all
on XP sp3 with netware clients for windows and in preparing for how we
are going to upgrade user desktops we have been testing DP and Shell on
some win 7 boxes, both the 32 bit and 64 bit versions. Also note that
with the netware clients for windows you have to turn of caching on each
and every workstation or the dp database gets corrupted and has to be
continually re indexed, forget to do this on one workstation and you are
wondering why am having to re-index. Turn off caching and we can run
months without re-indexing. Our database currently has 70 some panels
with multiple panels containing over a million records. We have been
building and using this system since 1991.
We have no trouble running dp and shell on win 7 32 bit natively and
with VDOS on win 7 32 bit and 64 bit. The trouble begins as soon as any
win 7 machine starts using the database all other users get a network
busy error and as soon as the win 7 box disconnects form the database
all other users start working again. When the win 7 box is connected to
the database it is the only one that can work in the database.
So, there must be some sort of caching or file locking going on with
windows 7 that I do not understand and it does it on the network drives.
Any suggestion as to what may be causing the problem
Thank you
Michael Shadel and Brian Finn
_______________________________________________
Dataperf mailing list
[email protected]
http://lists.dataperfect.nl/cgi-bin/mailman/listinfo/dataperf
