RE: Access 2002 Runtime - Windows XP Tablet PC

From: Rick (Rick_at_discussions.microsoft.com)
Date: 09/30/04

  • Next message: Paul Sanguinetti: "Digital signature" 
    Date: Thu, 30 Sep 2004 12:05:05 -0700

    The version of the msvbvm60.dll on the computer I had problems with was
    6.0.82.68 The version identified in the ospfilelist.txt file is 6.0.84.95
    The version on my machine is 6.0.92.37 I just copied the dll from my machine
    on to the problem machine and the install worked fine.

    "pvp" wrote:

    > May I enter the conversation to say that I have had a
    > client of mine who had ameaningless message about NT4 SP6
    > when installing under XP. I also tried to fix it as per
    > the article you mentioned and got nowhere. Also I got rid
    > of a Mac DLL from the list and that did no good.
    > So I'll hitch myself to your train and come for the ride.
    >
    > Thanks.
    > >-----Original Message-----
    > >I've finally identified a file that may be causing the
    > error to appear
    > >(msvbvm60.dll). I modified the ospfilelst.txt file
    > (located in the Packaging
    > >Wizard folder) and removed msvbvm60.dll. I then re-
    > packaged the applications
    > >and the subsequent install worked. My only concern at
    > this time is what
    > >effect this will have to my application. The
    > msvbvm60.dll is the Visual
    > >Basic Virtual Machine dll. The file is already located
    > on the system.
    > >
    > >"Rick" wrote:
    > >
    > >> I am not able to install Access 2002 (Service Pack 3)
    > runtime on systems
    > >> running Windows XP Tablet PC Edition Version 2002
    > Service Pack 1.
    > >>
    > >> I am getting the same error described in the Knowledge
    > Base Article 837150
    > >> http://support.microsoft.com/default.aspx?scid=kb;en-
    > us;837150&Product=acc
    > >>
    > >> The Office System Pack cannot be installed on this
    > system because it
    > >> requires Windows NT 4.0 Service Pack 6 or later.
    > >>
    > >> I have tried the workaround in the Article but it did
    > not work.
    > >> Any ideas?
    > >>
    > >> Thanks
    > >.
    > >
    >

  • Next message: Paul Sanguinetti: "Digital signature"

    Relevant Pages

    • Re: COBOL Functions
      ... You might want to check out using the DLL Cobol compiles for packaging ... functions that can be referred to by name, in a single source routine. ... This doesn't utilize the FUNCTION verb, but the DLL EXPORT and DLL ... Subject: COBOL Functions ...
      (bit.listserv.ibm-main)
    • Re: .NET dll works on one server and not another
      ... Seems like that using the Setup wizard for packaging my .NET site ... was adding this dll to the registery as well which was causing problems. ... > it exactly the same way on another server, the same asp code fails. ...
      (microsoft.public.dotnet.framework.interop)
    • Re: unexpected exception handler
      ... utilizes the DLL for the reason of packaging and better upgrade, ... You can't upgrade them independently anyway. ... What do you mean by "reason of packaging"? ... let the exported API in DLL throw an exception and let the EXE catch ...
      (microsoft.public.vc.language)
    • Re: activex registration/packaging
      ... you don't give enough info, what does the object tag look like, does the dll have and dependencies? ... Later versions are more restrictive about downloading and installing unsigned and unsafe control. ... The problem is packaging it so it ... registers itself on any other computer. ...
      (microsoft.public.dotnet.framework.aspnet)
    • Re: Emailing photos
      ... express and Picasa and now has reverted to showing the error notice ... You'll have to discover what is causing ... the .dll to become unregistered. ...
      (microsoft.public.windowsxp.photos)
    Loading