Windows Vista

We are working towards making VISUAL compatabile with Windows Vista for version 6.5.3

Please comment on what your plans are for adopting Vista (timeframes, concerns etc.)

More importantly if you have done any experimental testing of Vista and have encountered any issues, please post them in this discussion group.

We do not currently support Vista so any issues that you may have experienced could not be processed through the normal support channels.

Posting your experiences will help us uncover and resolve Vista problems during our development and testing phase so that they will not crop up again when we roll out the new version.

Find more posts tagged with

VISUAL - Enterprise General Discussions

Comments

fadi

We run visual 6.4.1 (SQL Server 2000) and visual 6.5.2 (SQL Server 2005) on windows vista business workstations. On 2 different location.
Few things I faced during using visual on vista.
Visual windows take around 20 to 30 second to open. Depend on what window the user opening.
many times the shortcut of the visual disappear from the program files menu or on desktop if the connection with the server is lost or the system not able to connect to map drive after startup, which in this case we need to pull the shortcut again for the users.
The performance in general is slow, on both versions but on 6.5.2 slower than 6.4.1.
Also detection for printers through visual take long time, when we try to view reports and print them, it can reach up to 1 min even if the report was 2 or 3 pages only.
Normal document printing through different application don’t face any delay except through visual.
If I can remember something else, I will post it here as well.

Best regards,

0712131256598360.doc

unknown

Sounds like your issues may be rooted in terminal services. I am using Vista Ultimate, Visual 6.5.2, SQL server 2005, with no issues other than that it seem slow in general. The speed of Visual is about the same on XP machines as well. We are going through our implementation with a go live date of 7/1.

systemsadmin

We are mostly an XP shop, but I find the overall Visual experience relies mainly on a client's hardware (i.e. cpu, ram, HD) and network throughput. We have experimented with a range of combinations from 802.11b to n and the likes of a PIII-800 up to higher-end Core 2 Quads, and we find that network throughput (with 6.5.3 at least) makes a bigger impact - a PIV with gigabit will have a better Visual experience than a C2D with 10/100. expectable as the apps run on the server across the network and have to interface with AD.

So far, the visual apps will run on anything on the client side (have tried XP, Vista and Windows 7, both x86 and x64 for each) equally well - naturally provided you have better equipment to handle the overhead of the newer OSes. We run into a 'base' window or report open time of about 4-6 seconds on even the fastest client combinations, so there is some level of authentication / server communication that doesn't seem 'fixable'. That being said, there may be low-level configurable elements of SQL Server that might need tweaking, or for instance the ability of the network equipment to utilize tech like jumbo frames or link aggregation...

We're running 6.5.3 on a dual Quad-core Xeon 3.0Ghz Poweredge with more or less all the trimmings (with SQL server 2005), and I confirm that the system resource usage on the server is negligible, so I'm open to ideas to close the performance gap myself...

Copyright © 2025 Infor. All rights reserved.