formathd error upgrading from Win98SE

Archived from groups: microsoft.public.win2000.setup_upgrade (More info?)

I'm trying to upgrade from Win98SE to Win2k Pro and
during the initial phase where it is 'discovering' about
my system, I get an error that aborts the install. The
message is:

formathd: invalid page fault in Kernel32.dll.

This file is on the CD, but not my hard drive. No matter
how many times I repeat, it still happens.

I've tried killing everything in the Task Menu to make
sure there are no conflicts, but nothing seems to work. A
clean install of Win2k on the machine works fine, but I
want to replace Win98 with programs/config intact.

Any ideas/suggestions would be greatly appreciated. Email
me at taylorms@mtaonline.net

Thanks,
1 answer Last reply
More about formathd error upgrading win98se
  1. Archived from groups: microsoft.public.win2000.setup_upgrade (More info?)

    Check this link
    http://support.microsoft.com/default.aspx?scid=kb;en-us;252725&Product=win20
    00

    Upgrading to Windows 2000 Causes Invalid Page Fault in Kernel32.dll with
    Quickbooks Installed
    View products that this article applies to.
    This article was previously published under Q252725
    SYMPTOMS
    During the system files portion of Setup, when you perform one of the
    following operations:
    Running the Windows 2000 Readiness Analyzer
    Running Winnt32 /checkupgradeonly
    Running Winnt32 and attempting to upgrade.

    You may receive the following error message:

    WINNT32 this program has performed an illegal operation.
    WINNT32 caused an invalid page fault in module KERNEL32.DLL at 0167:bff88396
    Registers:
    EAX=c00301a8 CS=0167 EIP=bff88396 EFLGS=00010202
    EBX=02ca8808 SS=016f ESP=02c9fed0 EBP=02ca0048
    ECX=00000003 DS=016f ESI=00000001 FS=21bf
    EDX=bff76855 ES=016f EDI=02003cb0 GS=0000
    Bytes at CS:EIP:
    53 56 57 8b 75 10 8b 38 33 db 85 f6 75 2d 8d b5
    Stack dump:
    CAUSE
    This error message can occur if Quickbooks, Powerbuilder, Cabnetware, or
    Oracle for Windows 95 is installed on your computer.
    RESOLUTION
    Quickbooks
    To resolve this issue, locate the Qbconv32.dll file and rename it to
    Qbconv32.dl_. If you find multiple copies of this file on the computer,
    rename each copy.
    Powerbuilder
    To resolve this issue, locate the following files and rename them to a .dl_
    extension. If you find multiple copies of these files on the computer,
    rename each copy:
    Pbctl050.dll
    Pbstr60.dll
    Pbudo050.dll
    Pbfrm050.dll
    Pbdse050.dll

    Cabnetware
    To resolve this issue, locate the following files and rename them:

    L323d.dll rename to - L323d.dl_
    L32cutes.dll rename to - L32cutes.dl_
    L32cutl.dll rename to - L32cutl.dl_
    L32cwv.dll rename to - L32cwv.dl_
    L32dlg2.dll rename to - L32dlg2.dl_
    L32estmt.dll rename to - L32estmt.dl_
    L32lay.dll rename to - L32lay.dl_
    L32mxs.dll rename to - L32mxs.dl_

    Oracle for Windows 95
    To resolve this issue, locate the following files in the orawin95 folder
    (by default) and rename them:
    NPL80.dll rename to - NPL80.dl_
    NR80.dll rename to - NR80.dl_
    NT80.dll rename to - NT80.dl_

    If you find multiple copies of a file on the computer, rename each copy.
    STATUS
    Microsoft has confirmed that this is a problem in Microsoft Windows 2000
    Professional.
    MORE INFORMATION
    You may also find the offending entry at the end of the Setupact.log log
    file. The entry would look something like the following example: Warning
    Modules:Access violation while checking c:\Program
    Files\Intuit\QuickBooks Pro 99\QBCONV32.dll

    If you are upgrading, you must rename the .dl_ file back to .dll after the
    upgrade completes so the program can start working again. After the upgrade
    completes, you can safely rename the file. Or you can uninstall the
    offending program. This issue only happens while the readiness analyzer or
    Winnt32 is running inside Windows 95 or Windows 98. After you install
    Windows 2000, you can rename the file back. This does not cause any issues
    and the program functions normally again.

    Another cause is a dynamic-link library (DLL) file that is included with
    Powerbuilder (Pbctlo50.dll). To resolve this issue, rename the file, let
    Setup continue, and after Setup or the Readiness Analyzer tool finishes,
    rename the file to its original name so that Powerbuilder works again.

    Cabnetware (or Cabware) may also cause this problem. This is Cabinet Design
    Software. Uninstalling the program resolves the issue. The readiness
    analyzer has problems with the following files from Cabnetware:
    L323d.dll
    L32cutes.dll
    L32cutl.dll
    L32cwv.dll
    L32dlg2.dll
    L32estmt.dll
    L32lay.dll
    L32mxs.dll
    The third-party products that are discussed in this article are
    manufactured by companies that are independent of Microsoft. Microsoft
    makes no warranty, implied or otherwise, regarding the performance or
    reliability of these products.

    To view a Microsoft Support WebCast about Windows 2000 setup issues, please
    visit the following Microsoft Web site:
    http://support.microsoft.com/servicedesks/webcasts/wc071800/wc071800.asp?fr=
    1


    Subbu
    This posting is provided "AS IS" with no warranties, and confers no rights.
Ask a new question

Read More

Windows