Jump to content

MERCURY127

Member
  • Posts

    236
  • Joined

  • Last visited

  • Days Won

    1
  • Donations

    $0.00 
  • Country

    Russian Federation

Posts posted by MERCURY127

  1. in generic, here is two veriants building process:

    DEBUG - for development. when u write own app, u use DEBUG version of ALL - windows kernel API libs, MS CRT libs, DX libs, etc. if and when u use debug libs, u can use VS internal or any other debugger at souce level, do step-by-step trace, trap exceptions, and see value any vers in properly type. its fast and cool. but these DEBUG libs contains many debug info, they big and slow, why they not include in usual windows redist.

    RELEASE - when app succefully writed and debugged, u recompile it w/o using degub versions libs. then app will use only standart libs, non dev, appear lesser and faster, and also cointains NO dubeg info, which can help end user crack or revesre app...

  2. 2 minutes ago, Tryphon said:

    Is it possible that this switch to protected mode failed at the beginning knowing that I got no error message

    yes, but u must see at least

    [000D76BB] Loading Vxd = vkd
    [000D76BB] LoadSuccess = vkd
    [000D76BB] SYSCRITINIT  = VMM
    [000D76BB] SYSCRITINITSUCCESS  = VMM

    in bootlog, as indication start prot mode...

    after Loading Vxd / LoadSuccess (hich is real mode part)

    will appear SYSCRITINIT / SYSCRITINITSUCCESS

    and DEVICEINIT / DEVICEINITSUCCESS

    for each vxd,

    and after [000D76BC] DEVICEINIT   = CONFIGMG

    begin processing of device tree.

  3. On 1/7/2019 at 5:30 PM, Tryphon said:

    vflatd.vxd, vmouse.vxd and vmd.vxd

    vmouse and vmd is mouse related. check ur mouse.
    vflatd is linear framebuffer related, are u sure, thar ur vc have this feature?

    anyway, this files can be deleted for test purposes.

    my suggestions:
    0) vmm32 is container:
    dos part - realmode starter (real vmm32.vxd),
    fyrst protected mode part - vmm vxd, main windows module (preboundled with vmm32.vxd, but its possible cut off in real vmm.vxd file),
    all other vxds,  added in container on install procedure.

    if u see that must ur vxds succefully loaded - so obviuosly, that VMM work good.
    then u can replece ur system vmm32.vxd to extracted vmm..vxd from ur distr, and place all other vxds from ur distr to system\vmm32 folder.
    after this, u can start windows with win /d:m command and look, which part make problems....

    but before it i suggest u check all ur hadrware, especially memory.

  4. i have exactly this problem on my pcie Radeon X600 (some powercolor oem) on VGA connection.
    my monitor is benq bl2411, 1920x1200. monitor wrongly detected as 1920x1440.
    when i try set res 1920x1200 - i get vertical panning...
    but if i use DVI - then 1920x1200 work good. but mon anyway detected as 1920x1440.
    98SE, Catalyst 6.2 or 5.9 - no diffs.

  5. last result (after using /m switch, or limiting of memory other methods):

    - vfat bsod now gone;
    - driver now is loaded successfully, w/o any errors;
    - Odyssey see wifi card, provided by driver;
    - but after scanning, list of networks remain empty. :(

    i think, it is all. THE END.
    but u can try this method (patching sys for vid/pid) with other (not so new) ralink pci cards.

  6. i not sure that it work now. my system now wont boot, i have bsod with VFAT error, instaed normal boot wiith code 10 yesterday.

    so, if anyone interesting, here is my patched RT28609X.SYS:
    9A904 -> 01 06 00 00 - first devid (now 60 53) - dword,
    9A908 -> 81 06 00 00 - sec devid - dword,
    9A90C -> 14 18 00 00 - realtek vid - dword.

    so u can write here own device for testing ur wifi cards.

    20181010001.1539178661.png

    2860.zip



×
×
  • Create New...