MARK install (5.0, beta2) - Unable to register component

[dhewitt]

I have always gotten an error/warning similar to this when I install MARK. I'm on WinXP Pro.

At the end of the installation, I get a message from the installer that says:

"Unable to register component: C:\WINDOWS\system32\lfpcd13n.dll

Specified module could not be found."

I have been using RMark and this glitch apparently doesn't bother the workings of MARK.exe, but does anyone know what this is, and whether I need to resolve it (and if so, how)?

[gwhite]

These messages about unable to register have to do with the graphics package. As long as you are able to graph okay, no problem.

I also have the problems fixed with the MARK 5.0 version concerning the design matrix. The problem was resolved when the Windows desktop icon has the installation subdirectory listed in the "Start in:" box for the Shortcut tab in the Properties box. This same fix is neededin the Start | All Programs menu approach to starting the program. The design matrix problem came down to the Mark_Int.exe file not locating a DLL correctly with the new version of the Visual Objects compiler. When the Mark_Int.exe file is executed starting in its subdirectory, everything works.

If you install the latest version, the setup should correctly set all of this up. If the MARK icon is not the red check mark across phi, then there may be a problem.

Let me know if you have problems with the newest setup.

Gary

[dhewitt]

These messages about unable to register have to do with the graphics package. As long as you are able to graph okay, no problem.

I also have the problems fixed with the MARK 5.0 version concerning the design matrix. The problem was resolved when the Windows desktop icon has the installation subdirectory listed in the "Start in:" box for the Shortcut tab in the Properties box. This same fix is neededin the Start | All Programs menu approach to starting the program. The design matrix problem came down to the Mark_Int.exe file not locating a DLL correctly with the new version of the Visual Objects compiler. When the Mark_Int.exe file is executed starting in its subdirectory, everything works.

If you install the latest version, the setup should correctly set all of this up. If the MARK icon is not the red check mark across phi, then there may be a problem.

When you say installation subdirectory, I assume you're referring to (default): C:\Program Files\MARK ? If so, when I just installed the new version that Evan sent the link to (beta2), the desktop icon DOES list that directory in the Shortcut Tab for the 'Start in:' field. However, the Start Menu icon that was created is a blank Windows .exe icon (not the checked phi) and the 'Start in:' field is blank. You can obviously change the icon by right-clicking and choosing the checked phi, and I can add the 'Start in:' field, but I'm not sure whether this indicates a lingering problem in the installation.

[cooch]

I have been using RMark and this glitch apparently doesn't bother the workings of MARK.exe, ...

The numerical optimization in MARK is handled by mark.exe. RMark is a 'different' front-end to passing arguments to, and parsing arguments from, mark.exe. All of the bugs in 5.0 to date have had to do with the 'classic' MARK install/gui. The mark.exe file itself is unaffected - and, as such, there is no reason not to be working with MARK 5.0, given you are using RMark.

[gwhite]

I just fixed the problem with the problem with the Start Menu icon. I don't thnk Evan has had time to copy the new file. Get it off the CSU site, and you'll have the version that should be fine.

You can just fix the icon yourself for now.

Gary

[cooch]

I just fixed the problem with the problem with the Start Menu icon. I don't thnk Evan has had time to copy the new file. Get it off the CSU site, and you'll have the version that should be fine.

You can just fix the icon yourself for now.

Gary

Nah - I got it within the past few minutes. You can download it from the phidot mirror:

http://www.phidot.org/software/mark/dow ... -beta2.exe

[dhewitt]

Just installed from the link Evan posted and all looks fixed to me (except that pesky .dll file).

Thanks