Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by ekx

  1. ok - problem solved! Had set VW to run with Administrative Privileges in order to allow file associations to be written to the registry.Also running in 'Compatibility Mode' for Win XPSP2. Running without Admin Priviliges and VW now 'sees' my printers. So used Admin Priv setting to write file associations then reverted to non-Admin Hope this may help others -e
  2. hi - I am running Vista Ultimate 64 and have VW 12.5.1 running onscreen but Print Setup says that there are no printers installed. Control Panel shows my installed printers and all other installed programs happily use my installed printers so my question is why VW does not recognise or detect my printers ? -e
  3. Received this reply from Aladdin ... HASP is USB 1.1 compatible. The USB 2.0 standard supports USB 1.1 devices, but if there is an issue with your hub downgrading, I suggest you contact the hub manufacturer. Regards Daniel Lewis HASP Technical Support Aladdin Europe
  4. I have a USB dongle which has migratde via upgrades from VW10 to my current 12.5 (Windows XP SP2) Is this dongle 'USB 2' compatible ? I ask because I believe that just one USB 1.1 device will reduce all USB ports to 1.1 speed under Windows Thanks for any help/advice Eric
  5. ekx

    VW12 will not run

    right on and thanks - QT had dropped off my system radar somehow. Reinstalled QT and VW working fine now Thanks for your prompt and excellent help -eric
  6. OK - this has me beat. VW12.01 (from CD) seemingly installs OK but will not run. there is a flicker of activity when invoked - then nothing. I have run chkdsk on my drives, uninstalled VW via deleting registry entries, reinstalled (to same & different dirs), deleted all Nemetschek/VW entries but still no program, no message, just nothing. Dongle lights up OK Program has previously worked up until yesterday - vital for my work so most urgent. All other stuff seems to be running OK so I am at a bit of a loss - maybe missing something simple. Would appreciate any help/advice thanks Eric Athlon 3400 64 - Win XP SP2 (all latest fixes) 1GB RAM, nVidia GS7800S Video 2 x 169GB SATA HD 1 x 200GB USB HD 1 x 300GB USB HD Zone Alarm Pro Trend Micro PC-Cillin 14
  7. Katie, I have tried all drivers available from Aladdin and still get the Standby BSOD. It is clear that, after all this time (nearly 3 months), neither Nemetschek nor Aladdin are interested in resolving this problem. I would therefore formally request a refund of my purchase price for this software as it is unusable on my machine. Eric
  8. Katie, It seems that the 1.8 version is Mac, I am PC-based and the drivers listed all seem to be the same 5.11 released at the end of September, unless you can tell me otherwise. Eric
  9. Katie, I am glad to see that you keep an eye on this thread. However, I would be grateful for a reply to my post of 28th Octob4er in which I asked you for the incident reference you have from Aladdin re your original report to them. Th reason I ask for this is that Aladdin in the UK can not trace your report until they have this reference. I would therefore appreciate it if you would give me this information. Eric
  10. Katie Would you please advise the incident reference you have from Aladdin, concerning your report of my Standby STOP error to them thank you Eric
  11. HAPPY 50Th ANNIVERSARY It is now 50 days since I reported this problem to Nemetschek. Sadly no solution has been offered, and contact has been minimal. Emails to Nemetschek Technical Support have been totally ignored. I am forced to copnclude that Nemetschek do not care about a problem which probably only affects a small number of users. This leaves only one course of action - Nemetschek, please advise me of procedures to return this defective product to you for a full refund. I hope that this can be accomplished easily otherwise, regrettably, matters would have to be taken further, fully publicised, and probably end up in court. in some sadness Eric
  12. 11 days on - any sign of a solution ? Patience wearing thin Eric
  13. Katie, Thank you for that reassurance. It is now a week on and I am hoping that Aladdin are near to or have a solution. Otherwise, regretfully, I would request your advice as to how I may return this faulty product for a refund. Eric
  14. Kate, Aladdin, Vectorworks, Is there any sign of a solution to my dongle problem ? I have been waiting now for over a week without any communication from concerned parties. An email direct to Aladdin has produced no response whatsoever, likewise with Nemetschek, as wewll as this board - does anyone care enough to deal with this and keep me informed? The whole episode raises serious concerns over the depth and value of support offered when purchasing Vectorworks. Eric
  15. Tom, thanks for the info. When I saw the date of the post I hoped that Alladdin had updated the driver but, altho' file dates and sizes are different these are the same SP2-compliant drivers isued earlier (and which I have tried). The latest file is dated 27th August whereas the earlier one is 16th August - perhaps just the GUI interface difference. Unfortunately for me the later driver file does not solve my Standby STOP error Thanks anyway Eric
  16. The following link may be of use in helping Aladdin to solve the problem. Perhaps you would refer them to this if they are not already aware. http://www.microsoft.com/technet/prodtechnol/winxppro/maintain/sp2mempr.mspx I am advised from the RIBA Ribanet Cobferenec that a similar problem has arisen with AllPlan, Athlon 64 cpu's, and SP2 Eric Eric
  17. Sorry to report same result. Stop with DRIVER_POWER_STATE_FAILURE and code 0x0000009F (but this code varies) Eric
  18. Not usually, and especially not at present. I will try that and report back Eric
  19. Any news on a solution to this problem ?? Ite getting tedious to keep removinmg the dongle thanks Eric
  20. quote: Originally posted by Katie: The problem is not in the driver of the dongle. In order for an OS to run smoothly, especially with all the changes to the OS with installation of SP2, all device drivers need to be updated. I believe this is also noted on Microsoft's knowledge base. Whenever you install new technology - in this case, SP2 - most of the drivers that link hardware to the operating system and allow for functionality need to meet the newer technology. I know most video card manufacturers released updates exclusively for purposes associated with changes to the OS in conjunction with SP2. Along with video card drivers, bios changes are also sometimes necessary for the identical purpose. You can choose to try my suggestions, or you can choose not to. Until the attempt to update drivers is executed, it's difficult to troubleshoot the scenario. Katie, your efforts are appreciated, I'm sure but a little introspection and a review of the thread will show, particulary in the above post, how I came to have the feeling of being brushed off. I also took the trouble to email you with my comments as a courtesy prior to posting. You might find on a second look that it is possible for Nemetscek to improve their service. However, lets get on and get this sorted - VW is too good a product to fall over with such a small problem.
  21. Katie, forgive me for reminding you of your post of 6th September "posted 06-09-2004 18:17 The problem is not in the driver of the dongle" and now today,8th September "The problem is in the Aladdin dongle driver, not in VectorWorks. We have established that as a truth" I do this not to score a cheap point but to emphasize how hard it has been to get you (Nemetschek, Aladdin) to take responsibility for your products. Were it not for SanFranN8 and myself pushing this fairly hard (and necessarily as our livelihoods depend on Vectorworks) I do not feel we would have got this far. I hope that this lesson may be learned, that you will be more receptive and attentive to us, the users, and, of course, for a rapid resolution of the problem. Eric
  22. Katie, Thank you for your assurance that my issue is under investigation. I appreciate that such matters can take time but SanFranN8 comments are certainly echoed by me. I will "wait patiently" (what else to do having invested in your software) Also waiting patiently will be the Royal Institute of British Architects (RIBA) on whose Ribanet Conference Board my problem and some responses have been posted. I trust that I will very shortly be able to report 'problem solved' back to the architectural community here in the UK.
  23. Can I expect any assistance from Nemetschek for my problem related above. It appears that this and the other related thread in General Discussion have moved on to other user's issues. My sympathies to them but may I also ask that my product be made workable ? That the problem I have raised be dealt with ? btw Katie SanFarnN8 explicitly stated the dongle light was ON in his/her post Any hope of any service here ??
  24. Wish I knew the answer - not yet available via Nemetschek or Aladdin, nor do either appear to want to take responsibility. All I can tell you is that the Aladdin SP2-compliant driver fixes VW and enables the program to work normally. The catch that I have experienced is that then going into standby with the dongle inserted results in the STOP error described above. If you remember to remove the dongle on going into Standby then all is well. Interesting to note that you too are running an Athlon 64 - perhaps this is relevant to Aladdin's driver problem ? Maybe some conflict with the VIA Hyperion drivers Hopefully somone from nemetschek will take this issue seriously and endeavour to provide support and service rather than blame everyone else. Eric
  25. Its diffciult for me to understand what part of "all drivers are up to date" you do not understand. May I repeat, all drivers are latest versions, bios is latest version. I hope this is clear to you I am certainly not unwilling to try suggestions, indeed I am actively seeking them. Your general observations and vague suggestions re video drivers & bios have already been anticipated, but the problem remains What then are Nemetschek's thoughts on an error which 1. has occurred after the dongle driver is updated 2. does not occur when the dongle is removed Eric
  • Create New...