Diese Seite mit anderen teilen ...

Informationen zum Thema:
Forum:
WinDev Forum
Beiträge im Thema:
21
Erster Beitrag:
vor 7 Monaten
Letzter Beitrag:
vor 6 Monaten, 3 Wochen
Beteiligte Autoren:
Robert Willis, Curtis, Tor-Bjarne, Fabrice Harari, Arie, Frans, robert willis, ChristoK!, GuenterP

I think PCSoft broke WB21 after releasing 22

Startbeitrag von Robert Willis am 22.10.2017 00:28

I have v22 installed and the keys were updated then. Now I'm trying to install WB21 on a laptop and the keys are not recognized and the setup will not extract the installation files. (64bits)

Antworten:

Hi

Nope, all versions works just fine together...

You just have a dongle driver compatibility problem. There is a faq on the pcsoft web site about that problem. Basically, you need to download the latest drivers from the aladdin web site and install them.

Best regards

von Fabrice Harari - am 22.10.2017 11:44
my dongles are glitchy as hell...

first all worked fine..
then dongles would work with 21 64=bit, but ONLY 22 32-bit = so I installed 22 32-bit
and that was fine...
and then would only work with 21 and 22 in 32-bit - so I installed 21 32-bit
and that was fine...
and at some point 64-bit was once again ok for both 21 and 22
and then it wasn't
and then it was
and then... well, you can see the pattern... currently I'm sitting in a 64-bit is fine again

C!!!

von ChristoK! - am 24.10.2017 15:49
Fabrice

Thanks for the input, but I did install latest drivers, pulled the dongle and reattempted.

The dongles seem to work for already installed products but NOT a fresh install of V21. Tried different machine, including a machine already a V22 where the keys function just fine.

von Robert Willis - am 25.10.2017 22:29
BTW, if you search for dongle, the LATEST document is 4 years old.

von Robert Willis - am 25.10.2017 22:38
BTW, why would they change the information, when the problem has been the same for as long as Windev has existed (nearly 25 years) and the solution the same too?

If you have a dongle problem, it's coming from the driver. And when you say that you installed the latest drivers, you fail to indicate where you found them, which version you tried, and so on...

So, as it's clear that you KNOW what the problem is not, you also clearly won't have any problem finding what it is...

Best regards

von Fabrice Harari - am 26.10.2017 11:42
The real problem is that PCSoft decided to use dongle security in the first place.

von Curtis - am 26.10.2017 14:39
yep, stuck in the 80's. I only wish I had to get new dongles for Windows 8 and 10 from Microsoft. I wonder why Microsoft doesn't use this cutting edge tech for copy protection.

von robert willis - am 27.10.2017 04:34
Hi, Microsoft is actually using your PC as their "dongle". Each PC has a UUID (Universally Unique IDentifier). Therefore you will not be able to install a certain Windows copy using the same serial number on a second PC - except for PCs from well-known makers. The BIOS of those PCs contains the Windows' type (Home, Pro ..., 32/64-bit) and serial number! Means, if your Windows 10 computer breaks down and you decide to buy another one from another maker (e.g. a home-made PC) you will have to buy another copy of Windows 10 too!

In contrast, PC Soft allows you to install their products on as many computers as you wish and work with them - provided that your dongle is connected to that computer which you are actually using.

von GuenterP - am 27.10.2017 05:37
Quote
- provided that your dongle is connected to that computer which you are actually using.


Unless your using remote desktop.

von Curtis - am 27.10.2017 15:04
Quote

Unless your using remote desktop.


The dongle still needs to be in the PC running Win/WebDev no matter if you are using remote desktop, teamvier , vnc or whatnot. :)

Unless PCSoft has come up with a Hard-lock server solution.

Cheers
Tor-Bjarne

von Tor-Bjarne - am 28.10.2017 11:43
So Fabrice how is it my responsibility to make the key work when if I go into install WebDev on a laptop that has never had a Wx Product, no hasp drivers ever and I go to install for the first time, putting in the dongle and it installs the drivers itself, will not light up, and can't find the dongle and extract the installation/setup files? How again is it my fault and not the installation of the tool?

I don't care they have had this for 25 years, if the process breaks THEY not me should provide a solution. This is my problem with PCSoft there is NO SUPPORT for the end users, especially in the USA. THEY DON'T support people. They don't care, otherwise there would be a bulletproof way to support and resolve.

von Robert Willis - am 28.10.2017 21:41
Hi

you are installing an older version (21), ie one coming with older dongle drivers on a brand new computer with the latest (ie much more recent) version of OS and there are compatibility issues... If you do not understand that problem, I'm not sure what I can do for you...

As to assigning responsibility, I couldn't care less...

I gave you THE solution I know have always been working for this kind of problems in order to try and help you... That's all.

You don't want to listen to me, it's ok... no skin of MY back.

Best regards

von Fabrice Harari - am 29.10.2017 12:27
Quote
Tor-Bjarne
Quote

Unless your using remote desktop.


The dongle still needs to be in the PC running Win/WebDev no matter if you are using remote desktop, teamvier , vnc or whatnot. :)


Did not work for me.

von Curtis - am 30.10.2017 15:15
Hi Curtis,

What did not work ?

Running Teamviewer against a PC with WinDev and dongle installed or installing the dongle?


Cheers
Tor-Bjarne

von Tor-Bjarne - am 31.10.2017 07:44
If PC 1 has the dongle plugged in and I remote desktop into PC 1 from PC 2 WinDev won't open because of dongle protection. I even tried putting a dongle in PC 1 and PC 2, but as expected that also did not work.

von Curtis - am 31.10.2017 14:34
Curtis,

afaik Windev has to be started before using RDP. It cannot be started from within a RDP session.
I had a spare laptop once and set is up to autologon AND auto start Windev. From that point I could use RDP and use WD.
Not very usable if you ask me.

von Arie - am 31.10.2017 15:22
I have never tried with RDP.
However, with any and all OTHER remote control toos I have used (teamviwer, anydesk, etc), I was ALWAYS able to start a windev (or webdev, or mobile) session on the remote computer (as long as that computer had its dongle in).

Best regards

von Fabrice Harari - am 31.10.2017 17:47
Hi,

When you start your RDP sessions, have you unchecked Smartcards and ports (And other plug & play units) within local resources before starting your session?

Cheers
Tor-Bjarne

von Tor-Bjarne - am 31.10.2017 23:12
Hello to you all,

RDP starting windev does not work. It is a feature in the Hasp dongle which prevents it.
Because enabling it would start multiple session of WD on one dongle.

von Frans - am 01.11.2017 18:00
Quote
Frans
Hello to you all,

RDP starting windev does not work. It is a feature in the Hasp dongle which prevents it.
Because enabling it would start multiple session of WD on one dongle.


Well that actually make sense :)

I have not tested this as Teamviewer is more than great for me working remote, and I need TV for my clients to.

Cheers
Tor-Bjarne

von Tor-Bjarne - am 03.11.2017 20:40
Zur Information:
MySnip.de hat keinen Einfluss auf die Inhalte der Beiträge. Bitte kontaktieren Sie den Administrator des Forums bei Problemen oder Löschforderungen über die Kontaktseite.
Falls die Kontaktaufnahme mit dem Administrator des Forums fehlschlägt, kontaktieren Sie uns bitte über die in unserem Impressum angegebenen Daten.