Jump to content

MERCURY127

Member
  • Posts

    242
  • Joined

  • Last visited

  • Days Won

    1
  • Donations

    0.00 USD 
  • Country

    Russian Federation

Posts posted by MERCURY127

  1. 17 hours ago, FantasyAcquiesce said:

    I tried this driver but the installer says Windows version is not supported...I need an interface for bluetooth to even function?

    You're right, I just found the screenshots I saved back then and they show version 2.1.3.0, release 060429. I apologize if I misled you, I was testing a lot of versions at the time and they all got mixed up in my head. Nevertheless, it was working for me at that particular time. I will try to repeat the experiments in the next few days and also try to run the BlueSoleil audio driver by writing inf similar to WIDCOMM, which seems to work in 98 without any problems (audio devices are installed and even some TV appears) but either doesn't see my dongle or requires a license and I don't know how to fix it.

     

    2023-01-25_132734.png

    2023-01-25_134146.png

    2023-01-25_134009.png

    2023-01-25_133405.png

    202301300012.png

    20230131004.png

    2023-01-30_181559.png

    2023-01-25_184900.png

    2023-01-26_200726.png

    2023-01-26_200829.png

    2023-01-30_182318.png

    2023-01-30_182532.png

    2023-01-30_183115.png

    2023-01-25_134101.png

    2023-01-30_193545.png

  2. i recently try make "generic" usb a/v driver, using wdmex and sys files from XP ...
    i test videocapture with cheap chinese endoscope (de-facto usb cam). its work with Amcap test app.
    i test sound playing and recording with cheap chinese usb soundcard. its work even in web browser Mypal.
    anyone want test? password 1 (protection from stupid antiviruses).

    USBAV9X.7Z

  3. Hi all!

    Before wmi9x run all WMI/WBEM instruments work good:
    104674558.png

    In wbemprox.log was only this strings:
    "ConnectViaDCOM, CoCreateInstanceEx resulted in hr = 0x0(Thu Apr 14 19:01:11 2022) :
    ConnectViaDCOM, CoCreateInstanceEx resulted in hr = 0x0(Thu Apr 14 19:01:13 2022) :
    ConnectViaDCOM, CoCreateInstanceEx resulted in hr = 0x0(Thu Apr 14 19:01:17 2022) :
    ConnectViaDCOM, CoCreateInstanceEx resulted in hr = 0x0(Thu Apr 14 19:02:28 2022) :
    ConnectViaDCOM, CoCreateInstanceEx resulted in hr = 0x0(Thu Apr 14 19:14:16 2022) :
    ConnectViaDCOM, CoCreateInstanceEx resulted in hr = 0x0(Fri Apr 15 11:28:32 2022) :"

    After - EVERYTHING WMI related is NOT WORK:
    104674909.png

    And in wbemprox.log now this:
    "NTLMLogin resulted in hr = 0x80041006(Fri Apr 15 11:28:32 2022) :
    Error loading module {F7CE2E13-8C90-11D1-9E7B-00C04FC324A8}, return code is 0x80041006(Fri Apr 15 11:28:33 2022) :
    NTLMLogin resulted in hr = 0x80041006(Fri Apr 15 11:28:33 2022) :
    Error loading module {F7CE2E13-8C90-11D1-9E7B-00C04FC324A8}, return code is 0x80041006(Fri Apr 15 11:28:33 2022) :
    NTLMLogin resulted in hr = 0x80041006(Fri Apr 15 11:28:33 2022) :
    Error loading module {F7CE2E13-8C90-11D1-9E7B-00C04FC324A8}, return code is 0x80041006(Fri Apr 15 11:28:33 2022) :
    NTLMLogin resulted in hr = 0x80041006(Fri Apr 15 11:28:33 2022) :
    Error loading module {F7CE2E13-8C90-11D1-9E7B-00C04FC324A8}, return code is 0x80041006(Fri Apr 15 11:28:33 2022) :
    NTLMLogin resulted in hr = 0x80041006(Fri Apr 15 11:28:33 2022) :
    Error loading module {F7CE2E13-8C90-11D1-9E7B-00C04FC324A8}, return code is 0x80041006(Fri Apr 15 11:28:33 2022) :"

    This or related errors appears everywere in WMI/WBEM tools...
    Why? And how fix this...

    Yes, i try "delete and recreate repository". many times. it not help...

  4. or use dos ramdisk like SRDISK, or write own pre-himem dos driver like BURNMEM, which will hide selected memory regions from himem via int15, or mod open-source himem XMGR for exclude some addresses... or use himemx or old himem from msdos, which [can be] limited first 64 MiB.

  5. yes, it is teoretically POSSIBLE.

    0) you must have patched IO.SYS and/or IFSHLP (but i can not remember what exactly patch need here...);
    1) you must dynamically load/unload properly version IFSHLP and/or network drivers by DEVLOAD.COM;
    2) you must use my ACPIOFF patch for win98 and boot to Command Prompt mode only, not direct to GUI;
    3) for solve 2) usb handoff issue after win98 exit, you must use true PS2 kbd and mouse.

  6. 15 hours ago, halohalo said:

    my screen went blank

    can u check that ur 1660ti is support legacy videos modes (EGA 640x350 and lower)?
    look as my problem with 1070....
    i partially solved it by patching vdd.vxd, and can boot to 9x gui, run games like Worms, but here remain (other?) problem with opening in MSDOS window... and i can NOT debug it even with softice. :(
     

  7. 19 hours ago, Joaquim said:

    maybe isn't compatible with WPA codification or something.

    WPA/WPA2 is not related with HW and low layer drivers. for work with WPA/WPA2 u need just good Wireless Supplicant, as Odyssey.
    with Odyssey's help i have succesfully connect to my router with WPA2-AES and that even work with absolute alien's for 9x device - USB dongle on RT2870.
    it means, that here can not be problems with WPA if ur HW is working properly.
    so please, check your hardware in a normal operating system, and only then think about buying new card.

  8. 1 hour ago, Joaquim said:

    i don't know do it

    - boot to 9x normal mode,
    - make W2KDISTR folder on ur 9x fat32 partition,
    - copy I386 folder from W2K setup disk to W2KDISTR,
    - make W9XBAK folder on ur 9x fat32 partition,
    - copy ur C:\IO.SYS COMMAND.COM MSDOS.SYS CONFIG.SYS AUTOEXEC.BAT to W9XBAK,
    - reboot to safe/plain/pure/clean msdos mode command prompt only,
    - rename ur 9x WINDIR to MYW9X,
    - delete ur MSDOS.SYS CONFIG.SYS AUTOEXEC.BAT
    - reboot machine,

    - cd W2KDISTR\I386,
    - run WINNT.EXE

    - in started w2k installer, select ur fat32 part to install, and say NO FORMAT,
    - if installer ask u for install to C:\MYW9X or C:\WINDOWS - force install to C:\WINNT
    - do installation to final, check, that ur w2k work normal (it "highly likely" :) that u get non-work EHCI USBs... this can fix later),

    - copy ur backed IO.SYS COMMAND.COM from W9XBAK to C:\ (with repl if need)
    - open C:\BOOT.INI in notepad,
    - find section and string

    [Boot Loader]
    timeout=30
    Default=multi(0)disk(0)rdisk(0)partition(1)\WINNT

    change "Default=" string to

    Default=C:\

    - find section and string

    [Operating Systems]
    multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000"

    add under this

    C:\="Microsoft Windows 98"

    - reboot machine,

    - on any next boot, now u will asked for select OS,
    - if u do all properly - u now will boot to 9x by default,
    - and now u must see pure MSDOS 7 prompt,
    - copy ur backed MSDOS.SYS CONFIG.SYS AUTOEXEC.BAT from W9XBAK to C:\ (with repl if need)
    - rename MYW9X to ur old WINDIR,

    - reboot again and check dualboot function...

  9. or B only. or G only. or disable WPA. or WEP. or turn ON something of.  

    On 6/6/2021 at 4:07 PM, Joaquim said:

    my hotspot was detected, on Windows 2000, with other mini card.

    is ur hotspot can be detected on w2k WITH THIS CARD?

  10. 1 hour ago, Joaquim said:

    my hotspot was detected, on Windows 2000, with other mini card.

    is wrong answer... i again ask:
    "which setiings is used?"
    ie:
    - what rediofrequency used? 2.4 or 5 GHz?
    - which wifi standart used? 11a|b|g|n?
    - what cipher?
    - what auth method?

    WHAT EXACTLY NAME AND MODEL UR WIFI HOTSPOT?
    if hotspot have any optons for change settongs?

×
×
  • Create New...