PMView.com

Welcome Guest ( Log In | Register )

 
Reply to this topicStart new topic
> PMView 3.05 registration problem - continued - Full version claims it's not.
Guest_Teijo Kaakinen_*
post Jan 29 2004, 06:45 AM
Post #1





Guests






Sorry for continuing in another topic - I couldn't post a reply, couldn't find my password, and didn't receive an e-mail notification despite going through the process.... so here goes a long post:

I tried to reinstall using a new download as you suggested, recording the steps.

Redownload file from:

/RIP.FileDownload?PRODUCTID=[WHATEVER]&PASSWORD=[WHATEVER]]https://secure.bmtmicro.com/[whatev....ATEVER]

Saved file name: f:commdlpmview305os2full.exe
File size: 5486652 (A comparison shows the size is exactly the same as the previous one, which I also kept.)

f:
cd commdl
pmview305os2full.exe

>next
>I agree
>Next (PMView Pro in e:appspmview, DLL in e:dll - yes, it's in libpath)
>Install
>Yes
>Skip this file (pmvddrop.dll to be relplaced is the same date and size)
>Ok
>No (The class pmvddrop is already registered with the same dll)

A whole bunch of OS/2 windows momentarily appear and disappear, too quickly for the eye to follow, after which I get the message "Installation has completed..."

>Ok

Doubleclick on PMView Pro folder on the desktop.
Doubleclick on PMView Pro icon in the folder

The program tells me:
"You are on day 14 of your 31 day evaluation period."

>Ok
>Close

>Help
>About

The program tells me:
"You are on day 14 of your 31 day evaluation period."

Well, at least we have some improvement - I no longer need to count every peek at help as another day!

Close program.

Check file names:
04-01-28 5:18 0 Filters
03-12-10 9:20 132224 37 gstarted.pdf
03-05-06 20:02 36811 0 makedefv.exe
03-05-06 18:39 5200 0 MakeDefV.ico
03-05-02 16:51 1577 0 PMV30HTK.DLL
04-01-23 19:58 2640268 0 PMView.exe
04-01-23 20:14 488245 0 PMView.HLP
03-04-11 18:53 15336 0 pmview.ico
03-05-16 21:12 1667209 38 pmview.pdf
03-06-07 8:21 7902 0 PMView.tip
04-01-29 10:12 0 ReadMe
04-01-28 5:18 0 Scripts

Ignore filters, documentation, icons and scripts, and look for duplicate exe and dll files on the path.

xdir /s /e d:PMV30HTK.DLL
xdir /s /e d:PMView.exe
xdir /s /e d:pmvddrop.dll
xdir /s /e e:PMV30HTK.DLL >found e:APPSPMViewPMV30HTK.DLL
xdir /s /e e:PMView.exe >found e:APPSPMViewPMView.exe
xdir /s /e e:pmvddrop.dll >found e:DllPMVDDrop.DLL

No duplicates.

Now, let's try again.

Start by deleting the product:

Open WarpIn
Highlight PMView Pro
MB2 click
>Deinstall all packages
>OK
>Yes, WarpIn should unlock and delete pmvddrop.dll

A bunch of errors. Save log file.

Deleted object ""
Deleted object ""
Deleted object ""
Deleted object ""
Cleared profile entry "USERPMView 3.0"
Cleared profile entry "USERPMView 3.0InstallerProgramPath"
Error with File "e:APPSPMViewlnshadow.exe". OS/2 reported: "SYS0002: 指定されたファイルが見つかりません。"
Error with File "e:APPSPMViewmigrate.exe". OS/2 reported: "SYS0002: 指定されたファイルが見つかりません。"
Error with File "e:APPSPMViewRegister.DAT". OS/2 reported: "SYS0002: 指定されたファイルが見つかりません。"
Error with File "e:APPSPMViewregister.exe". OS/2 reported: "SYS0002: 指定されたファイルが見つかりません。"
Deleted object ""

(The strange characters are Japanese and say the file wasn't found.)

A red X remains in the WarpIn database.

Now try again with the saved "pmview305os2full.exe"

f:
cd commdl
pmview305os2full.exe

>next
>I agree

Ah, this time the default program path for PMView Pro is "M". It's grayed out, too, and unchangable. No matter, we'll see what happens. Place DLL in e:dll .

>Next

-You have specified the following directories which are not valid:
-M
-Please correct these errors first.

>OK

I guess that won't work.

>Cancel
>Yes, I do want to exit WarpIn

Open WarpIn database.
Remove database entry for PMView Pro
>Yes

Close WarpIn

f:
cd commdl
pmview305os2full.exe

>Next
>I agree
>Next (PMView Pro in e:appspmview, DLL in e:dll)
>Install
>Yes
>Yes (The class pmvddrop is already registered with pmvddrop.dll, but since the file no longer exists I do want to reregister it with the new file.)

Again, a whole bunch of OS/2 windows momentarily appear and disappear. I catch a glimpse of a line that says something about tcpip.

-do you want to have WarpIN have restart the workplace shell
>yes

... only it wasn't restarted, only shut down. Shut all processes down. Nothing happens. Call up CAD commannder. Invoke a console window. Setboot -b.

After reboot,

Doubleclick on PMView Pro folder on the desktop.
Doubleclick on PMView Pro icon in the folder

The program tells me:
"You are on day 14 of your 31 day evaluation period."
>OK
>Close

That's all I can think of. At least I'm not running out of evaluation days as quickly.

What should I try next?

Teijo Kaakinen
Go to the top of the page
 
+Quote Post
Peter
post Jan 29 2004, 08:46 AM
Post #2


Forum Member


Group: Admin
Posts: 661
Joined: 14-March 00
From: Wilmington, North Carolina
Member No.: 3



Sounds like WarpIN is messed up on your system.

The "M" thing is a WarpIN bug.

So much for the new installer...

At this time I would suggest that you completely UNINSTALL PMView. Make sure that the PMView directory is removed and that no files are left from the old installation.

Then try to install again.

Thanks,
Peter


--------------------
Peter Nielsen (peter@pmview.com) "If you can dream it, you can do it" JFK.
Go to the top of the page
 
+Quote Post
Peter
post Jan 29 2004, 08:50 AM
Post #3


Forum Member


Group: Admin
Posts: 661
Joined: 14-March 00
From: Wilmington, North Carolina
Member No.: 3



Oh, BTW, the reason you end up with the trial version is because WarpIN is not executing REGISTER.EXE that is used to bulid the full version.

So, you definitely got the right file. The problem is that WarpIN is not doing its work correctly...

Thanks,


--------------------
Peter Nielsen (peter@pmview.com) "If you can dream it, you can do it" JFK.
Go to the top of the page
 
+Quote Post
Peter
post Jan 29 2004, 04:38 PM
Post #4


Forum Member


Group: Admin
Posts: 661
Joined: 14-March 00
From: Wilmington, North Carolina
Member No.: 3



QUOTE
Again, a whole bunch of OS/2 windows momentarily appear and disappear. I catch a glimpse of a line that says something about tcpip.
This is where MAKEDEFV.EXE (the program for setting the associations) and REGISTER.EXE (the registration utility) should be run. For some reason, WarpIN obviously fails to do that.

QUOTE
-do you want to have WarpIN have restart the workplace shell


Try installing again and answer "NO". (On my system, WarpIN locks up totally every now and then if I answer YES).

Thanks,




Edited By Peter on 1075412487


--------------------
Peter Nielsen (peter@pmview.com) "If you can dream it, you can do it" JFK.
Go to the top of the page
 
+Quote Post
davidfor
post Jan 30 2004, 06:48 AM
Post #5


Forum Member


Group: Members
Posts: 3
Joined: 29-January 04
From: Australia
Member No.: 174



Peter,

My experience is basically the same as Tiejo's. As you guessed, MAKEDEFV.EXE didn't get run. The only thing I can add, is that I ran the install a few times, and positioned the installation windows so I could see what the command windows that came up. In each case they would flash up and close, but, they seemed to be saying that the file to be run wasn't found. That suggests the files are either not being copied, or, that WarpIn is using the wrong path to try and run them.

Anyway, I have solved my problem by using WIC.EXE to expand the installation file, and then copying and running REGISTER.EXE myself.

I also expanded the 3.04 installation files, and I couldn't see a difference between it and 3.05. So, now I'm wondering what has changed on my machine since I installed 3.04, as it went in with out any problems. If I can work it out, I'll tell you.


--------------------
--
David
Go to the top of the page
 
+Quote Post
davidfor
post Jan 30 2004, 07:33 AM
Post #6


Forum Member


Group: Members
Posts: 3
Joined: 29-January 04
From: Australia
Member No.: 174



Ok, I worked out what the change was: Jonathan de Boyne Pollard "OS/2 Command Line Utilities".

I just removed the two likely looking files that it adds: "COPY.CMD" (which calls "CopyStd.exe") and "CMD.EXE". "CopyStd.exe" is also part of the above package. Without these, the 3.05 install works perfectly. This reminds me of the problems the IBM installer had when 4OS/2 was installed.

I might have a look over the weekend to see which is the real culprit.


--------------------
--
David
Go to the top of the page
 
+Quote Post

Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 



Lo-Fi Version Time is now: 25th May 2018 - 12:21 AM