| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 160.1 | | JAMIN::WASSER | John A. Wasser | Thu Mar 13 1997 16:45 | 11 |
| > Any clues to the causes and/or resolutions for this error on a
> Win95/PW32 system?
The PATHWORKS 32 Setup Utility apparently failed to remove the
"PATHWORKS Licensing Agent (LAN Manager)" that was installed
by "PATHWORKS for Windows 95".
Make sure that the DECLICL.INF file is still in the \W95\INF
directory, then go to the Network control panel and remove:
PATHWORKS Licensing Agent (LAN Manager)
|
| 160.2 | | VMSNET::S_VORE | Smile - Mickey's Watching! | Fri Mar 14 1997 10:44 | 11 |
| Customer's system was never running PATHWORKS for Windows 95. It was
running WfW & v6's protected-mode license bits though, but there's not
a "PATHWORKS Licensing Agent (LAN Manager)" in her control panel to
remove.
Her scenario was this: WfW+v6, upgraded to Win95, installed PW32
Next suggestion please?
|
| 160.3 | | JAMIN::WASSER | John A. Wasser | Fri Mar 14 1997 15:10 | 18 |
| > Her scenario was this: WfW+v6, upgraded to Win95, installed PW32
I don't know how Microsoft intends the WfW->W95 upgrade to
to deal with installed software. Apparently it kept parts
of the DECLICL network service but lost the knowledge that
it was installed.
> there's not a "PATHWORKS Licensing Agent (LAN Manager)" in her control panel
> to remove.
>
> Next suggestion please?
Edit SYSTEM.INI.
Remove "instlicl.dll" from "[boot] drivers=", if present.
Remove "declicl.vxd" from "[386enh] network=", if present.
|
| 160.4 | AAAAAACK! | VMSNET::S_VORE | Smile - Mickey's Watching! | Mon Mar 17 1997 09:58 | 12 |
| Removed INSTLICL from system.ini. DECLICL was not there. Now it's even
worse :-{
The error is still there; could not open registry key.
However, other than normal "loading" and copyright messages, that's the
only license messages -- now it doesn't even try to get a license at
all (remember, in .0 it was requesting from the wrong group but was at
least requesting)!
|
| 160.5 | | JAMIN::WASSER | John A. Wasser | Mon Mar 17 1997 10:10 | 9 |
| > Removed INSTLICL from system.ini. DECLICL was not there.
I guess for Windows 95 it is listed in the Registry instead
of in the SYSTEM.INI file.
Edit the registry and remove the tree:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VxD\DECLICL
|
| 160.6 | License Wars - the Saga Continues... | VMSNET::S_VORE | Smile - Mickey's Watching! | Mon Mar 17 1997 12:25 | 33 |
| >Edit the registry and remove the tree
It wasn't there. Hmm, just for grins, let's add it.
Rebooted. Now this message isn't in the PWLog any more, but pw32
license bits still not requesting license.
Next stop, Network control panel - configure PW License Requestor.
Reboot again. same deal. Ah, noticed that the log file says
"PATHWORKS Licensing" still rather than "DEC LAN Manager..."
Once more dear friend into the fray... regedit, search for
INSTLICL-found it as HKEY_LOCAL_MACHINE / System / CurrentControlSet /
control / SessionManager / Known16DLLs / INSTLICL.DLL Ok, let's
remove that. Reboot. Check PWlog-
PATHWORKS License Requestor is STILL there! After that loads, though,
PNLT32 loads but not PNLR32.
Ran PNLR32 by hand, it tried to get licenses from the right group
(didn't obtain one, but customer's off to check the server to see that
some are actually available).
Control Panel, Network, remove DEC LAN Manager licensing, reboot.
PATHWORKS stuff still there (before CORE003N) but all PW32 license bits
gone.
Run PW32's SETUP to add PW32 license bits back again.
Same thing in PWLog file... OLD requestor runs, then CORE003N, then
NEW Transponder loads, then nothing else licensing-related.
Next?
|
| 160.7 | | JAMIN::WASSER | John A. Wasser | Mon Mar 17 1997 14:44 | 14 |
| > regedit, search for INSTLICL-found it as HKEY_LOCAL_MACHINE /.../
> Known16DLLs / INSTLICL.DLL Ok, let's remove that. Reboot.
> Next?
Do the same for DECLICL.VXD.
If that doesn't work, search every file in the damn disk to
find one that mentions DECLICL.
My guess is that the upgrade from Windows for Workgroups to
Windows 95 decided that the VXD called "DECLICL.VXD" should
be run at startup time and it made a note of that SOMEWHERE.
|
| 160.8 | | VMSNET::S_VORE | Smile - Mickey's Watching! | Mon Mar 17 1997 14:59 | 12 |
| We had already checked for "DECLICL" - didn't appear in her registry.
"search every file..." hmm, not a terribly pleasent prospect.
I agree with your guess; we do need to figure out where this stuff
goes -- I'm *sure* this won't be the only person to say...
"I was running WfW with v6, upgraded to Win95 and all was working.
Now I want to install PW32, but it won't work right!"
|
| 160.9 | | JAMIN::WASSER | John A. Wasser | Mon Mar 17 1997 17:35 | 18 |
| > "search every file..." hmm, not a terribly pleasent prospect.
Remember, this is Windows 95!
Start -> Find -> Files or Folders
Named: "*.*"
Look in: "C:\"
Checkmark "Include subfolders"
Select the "Advanced" tab
Containing text: "DECLICL"
Click on [Find Now]
You may want to try "*.INI" first since that is the most
likely hiding place after the Registry. That should be a fairly
quick search. If that fails you can try "*.*".
|
| 160.10 | | VMSNET::S_VORE | Smile - Mickey's Watching! | Tue Mar 18 1997 07:52 | 4 |
| been there, tried that. nothing found. nothing found in the registry.
customer giving up & starting from scratch. we're attempting to
duplicate the situation here for our records and future customers.
|
| 160.11 | Move Along Home... | VMSNET::S_VORE | Smile - Mickey's Watching! | Tue Mar 18 1997 10:19 | 12 |
| went throught the WfW+PW6 -> W95 upgrade scenario several times here,
with various amounts of failure, but never were duplicated exactly the
customer's problem.
In our case, the old transponder does not load, the old requestor runs
(after CORE003N) but requests nothing as the old transponder's not
there, then the new transponder loads and the new requestor runs just
fine.
Recommendation for anyone else... don't get into this mess :-) Remove
pw5 before upgradeing from WfW to Win95.
|
| 160.12 | | JAMIN::WASSER | John A. Wasser | Tue Mar 18 1997 15:02 | 17 |
| >>> LICL1012E: Could not open registry key:
>>> SYSTEM\CurrentControlSet\Services\VxD\DECLICL (Error)
>> search every file in the damn disk to find one that mentions DECLICL.
> been there, tried that. nothing found.
The message contains the text "DECLICL" so the text almost
certainly exists in SOME file or SOMEWHERE in the Registry.
Did you actually have them search ALL files?
> customer giving up & starting from scratch.
They're going to re-format their hard disk and re-install
Windows 95? Anything short of that may not solve the
problem.
|
| 160.13 | | JAMIN::OSMAN | Eric Osman, dtn 226-7122 | Thu Apr 17 1997 15:45 | 7 |
| I had a problem in the past where registry complaints were traced
back to attempting installation from a username on the w95 system that
didn't have the administrative privs to manipulate the registry.
Is this perhaps your situation ?
/Eric
|