Error code 31 in Windows 2000 environment

Sysprogs forums › Forums › WinCDEmu › Error code 31 in Windows 2000 environment

Log In Register Lost Password
Viewing 11 posts - 1 through 11 (of 11 total)
  • Author
    Posts
  • June 21, 2009 at 16:10 #78
    Anonymous
    Participant

    Hi,

    I did install the WinCDEmu in my computer.

    Windows XP 32Bit SP3 : Good !
    Windows XP 64Bit SP3 : Good !
    Windows Vista 32 SP2 : Good !
    Windows Vista 64 SP2 : Press F8 key whilst boots and selecting the “Disable Driver Signature Enforcement” boot option every time. then it work correctly.
    Windows 7 32Bit RC : never try it.
    Windows 7 64Bit RC : Press F8 key whilst boots and selecting the “Disable Driver Signature Enforcement” boot option every time. then it work correctly.
    Windows 2000 SP4 : error code 31

    Do not work in Windows 2000 environment.
    In control painel has a DVD/CD Drives called Virtual CD drive.
    It is with error code 31.

    PS.
    I will pay for digital signature, if I can.
    😉

    June 21, 2009 at 16:25 #1032
    support
    Keymaster

    I did not test it on Windows 2000, however, I suppose, that the problem is due to some of API functions not supported by Windows 2000. Could you please perform a simple test?:
    1. Try forcibly loading VirtDiskBus driver (net start VirtDiskBus from command line).
    2. If the driver loads successfully, skip the next step.
    3. Download Dependency Walker from http://www.dependencywalker.com/%5D and open VirtDiskBus.sys with it. Observe, which functions are not provided by Windows 2000 kernel and post them here.
    4. Repeat steps 1-3 for BazisVirtualCD driver.
    As soon as you provide enough information to pinpoint the problem, I’ll be able to release an update (if it is not related to some key functionality not supported by Win2K).
    P.S. Regarding the digital signatures and x64, I’ll soon release an update based on Authenticode technology, that will allow running WinCDEmu on such machines after importing SysProgs.org certificate and enabling “driver test mode” via bcdedit. See the http://wincdemu.sysprogs.org page in one-two weeks.

    June 22, 2009 at 01:33 #1033
    Anonymous
    Participant

    Thank’s,

    I try dependencywalker, and VirtDiskBus.sys has no error.

    But BazisVirtualCD.sys has an error at NTOSKERNL.EXE

    Ordinal : N/A
    Hint : 1405 (0x057D)
    Function : _aulldvrm

    June 22, 2009 at 01:50 #1034
    Anonymous
    Participant

    Anyway,

    bcdedit /set loadoptions DDISABLE_INTEGRITY_CHECKS

    It’s not work, because KB938194(Windows Update)

    June 22, 2009 at 02:05 #1035
    Anonymous
    Participant

    your meaning [ bcdedit /set testsigning on ] …..

    June 22, 2009 at 06:28 #1036
    support
    Keymaster

    Yes, bcdedit testsigning on will help after I release a new version with SysProgs.org signature.
    Could you please try the following driver on Win2K: http://wincdemu.sysprogs.org/win2kfix/BazisVirtualCD.sys
    If it works for you, I’ll include the Win2K build in the next release.

    June 22, 2009 at 10:00 #1037
    Anonymous
    Participant

    Thank’s,

    But it did’t work.

    DependencyWolker said “No PE signature found. This file appears to be a 16-bit DOS module.” and “Error: At least one file was not a 32-bit or 64-bit Windows module.”

    June 22, 2009 at 10:08 #1038
    support
    Keymaster

    Maybe, your browser took the unknown .sys file as a text file and corrupt it. Try the following link: http://wincdemu.sysprogs.org/win2kfix/BazisVirtualCD.zip

    June 22, 2009 at 10:32 #1039
    Anonymous
    Participant

    Thank’s,

    This time it gave to me a pure blue screen. 😀

    DependencyWolker said no error.

    And blue screen said,
    *** STOP : 0x000000D1 (0x07CB4000, 0x00000002, 0x00000000, 0xF5C80D64)
    DRIVER_IRQL_LESS_OR_EQUAL
    *** Address F5C00D64 base at F5C80000, DateStamp 3d90d765 – Cdr4_2K.SYS

    June 22, 2009 at 10:37 #1040
    support
    Keymaster

    As the crash is inside Cdr4_2K.SYS, most likely, it is a bug in this driver. For example, it can expect a full SCSI device behind the virtual drive and fail, when it cannot find such device.
    Sorry, but it is almost impossible to pinpoint the problem without having debug information for Cdr4_2K.sys. You can try sending a minidump to the authors of this driver; maybe they’ll release a patch.

    October 29, 2009 at 01:15 #1041
    Anonymous
    Participant

    Thank’s lot.

    The Cdr4_2K.SYS is Windows Media Player’s component.
    And it can uninstall separately !

    For example.
    WMP 9 : rundll32 advpack.dll,LaunchINFSection C:winntinfroxio.inf,Uninstall
    WMP 7/7.1 : Controlpanel – select uninstall WMP7/7.1 – select “Adaptec CD Creater plugin”

    In my case WMP9 was installded, and I was uninstall this module separately, then WinCDEmu run GREATLY!

    Anyway,

    I tried Windows 7 32Bit RC environment and it run GOOD!

    so,

    Windows XP 32Bit SP3 : Good !
    Windows XP 64Bit SP3 : Good !
    Windows Vista 32 SP2 : Good !
    Windows Vista 64 SP2 : Next version will run with no F8 key.
    Windows 7 32Bit RC : Good !
    Windows 7 64Bit RC : Next version will run with no F8 key.
    Windows 2000 SP4 : Next version and/or http://wincdemu.sysprogs.org/win2kfix/BazisVirtualCD.zip run Good ! (*1)
    *1 : need uninstall Cdr4_2K.SYS.

  • Author
    Posts
Log In Register Lost Password
Viewing 11 posts - 1 through 11 (of 11 total)
  • You must be logged in to reply to this topic.