Jump to content

schwups

Member
 View Profile  See their activity

  • Posts

    1,292

  • Joined

  • Last visited

  • Days Won

    5

  • Donations

    0.00 USD 

  • Country

    Germany

 Content Type 

Everything posted by schwups

  1. schwups
    Can you change the language of XnView? (Tools>Options>Interface or xnview.ini [start] Language= ) It sticks to English. Possible is to copy the xnview.ini of "Application Data XnView" to the program folder in the case that the file doesn't exist in the program folder of XnView. Then set the desired language in the ini file. This file can disappear and XnView sticks to English again. I can set Tools>Options>System integration>Save options>as ini file in folder to "XnView". Then I must set the desired language in the ini file. Afterwards the language selection works. The other "Save options" for the ini allow no selection. XnView Version 2.34. This behavior occurs with three machines here. OS WinME
  2. schwups
    This is certainly no bug of KernelEX. Probably something is missing. What error message you have? Did you install the WindowsInstaller 2.0 ? The msiexec.exe should be in your systemfolder.
  3. schwups
    What exactly do you mean? What's different with your setup? Usually KernelEX 4.5.2 (14 November 2011) without Kext is easy to install and use. The only requirement is Microsoft Layer for Unicode MSLU (unicows.dll version 1.1.3790.0 (07 December 2004)). Don't copy an older version of unicows.dll in your system folder.
  4. schwups
    The button works if I write the planned file type (with name) into the "Object name" box. The type must be the same in the "save as Type" box. On XP it works better.
  5. schwups
    FS Image Viewer 5.4 (OS WinME KernelEX 4.5.2015.8): The "Save as" function (post 399) and the Options button (post 402) work here, if KernelEX is enabled. They fail, if I disable KernelEX. Kext (kstub822) doesn't matter. So far I testet on one machine and KernelEX 4.5.2015.8 only.
  6. schwups
    v1.4.6.0 - Fixed random empty code type selection under Windows ME - GUI improvements to eliminate confusion about utility of 'code type' selector "Random empty code type selection under Windows ME" =>It hasn't occured anymore (tested with 82.16 and 82.69). Where exactly was the problem?: "GUI improvements ..." => much better v1.5.1.0: Fixed wrong code sequences in the ini file for WinME (bug carried on since v1.4.4.0)... => Now Win ME shuts down with safe (a) code, too (tested with 82.16 and 82.69) .
  7. schwups
    Before running the CodeType entry is 1. I repeated the first start without patching several times. Sometimes the box was empty (the scroll down menu shows all modes), but sometimes there was "safe" inside. Odd
  8. schwups
    But I can select all modes.
  9. schwups
    The code type box is empty with the first run only.
  10. schwups
    OK, "wide" and "full" works. ME users should see, that they must select these options. Obviously the "safe mode" is the default one, if you don't select "code type" (empty box). And another thing, I see two differences between code of rloew in the first post and your ShutdownPatcher: 144: AC -> C3 31F6E6: E6 54 E5 FF -> C2 05 00 00 31FCAC: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 -> 3C 04 74 08 3C 25 74 04 3C 32 75 02 B0 52 89 44 24 04 E9 0D 4F E5 FF Segment length at 0x144: - 0x2D6EC4 Call at 0x31F6E6: - new: 0x5C2 Additional code at 0x31FCAC: - new: 3C 04 74 08 3C 25 74 04 3C 32 75 02 B0 52 89 44 24 04 E9 0D 4F E5 FF 18
  11. schwups
    I checked the first option "Patch installed driver in place". Applies "code type" option under the second option to the first, too?
  12. schwups
    ShutdownPatcher Version 1.4.5.0: I tested it on the machine with the NV7800GT and driver 82.16 - OS Win ME. It patches with the not working and not revised code on ME. log: 2015.08.04 11:39:34 Microsoft Windows ME 4.90.3000 ================================================================= • PATCHING File path: C:\WINDOWS\SYSTEM\nvcore.vxd Processing nvcore.vxd version: 82.16 [size: 3276893 bytes] Segment length at 0x144: - old: 0x2D6EAC - new: 0x2D6EC0 Call at 0x31F6E6: - old: 0xFFE554E6 - new: 0x5C2 Additional code at 0x31FCAC: - old: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 - new: 3C 04 74 08 3C 32 75 02 B0 52 89 44 24 04 E9 11 4F E5 FF 14 Result: DONE. Details: Backup file saved as C:\WINDOWS\SYSTEM\nvcorebk.vxd
  13. schwups
    Yes the power supply shuts down on both machines, 7800GT with driver 82.16 and 7900GS with driver 82.69. Apparently it works as desired.
  14. schwups
    Is this code to test for 98SE only or also for ME? It has a G72. Some years ago I tried to install the driver 81.98 for G70 and G73 without success. So I thought that 81.98 doesn't work with NV 7xxx cards.
  15. schwups
    @rloew That did not help . 7800GT PCIE - driver 82.16 / Intel G41 chipset
  16. schwups
    - I use ME. I install 98SE for rare test purposes only. - Yes it's the DOS cursor on black screen.
  17. schwups
    I'm not sure, but I think driver 81.85 should be the first affected driver, because 77.72 doesn't exhibit the shutdown bug. 77.72 supports 6xxx series. I seem to remember the 7xxx series require 82.16 or 82.69. I never heard that one of 5xxx series is affected, which corresponds to my experience, too. Geforce 6xxx series is affected, but I never used a 6200. I'm not sure about this card.
  18. schwups
    Machine (NV 7800GT PCIE), driver 82.16: After I corrected "45 4E" to "15 4F" the protection error is gone , but the power supply doesn't shutdown and the cursor remains . And there was no Scandisk after shutdown. A subsequent manual scandisk didn't find any errors .
  19. schwups
    It shouldn't matter as long as the Patch ends up in WINDOWS\SYSTEM\NVCORE.VXD.If it is not working, try changing the second and third bytes of the long Patch from 32 75 to 24 72. If this works let me know. Yes, I tried "24 72", but without success. The power supply doesn't shutdown and the cursor remains. It seems, that there is no scandisk on next boot (no FS error) with "32 75" or "24 72". I'll check this once more. I also modified nvcore.vxd of the driver 82.16 according to your specifications on a second machine (NV 7800GT), but again without success. I got an protection error on start. I'll check this once more. I used the HEX-Editor MX. Is it possible, that in this case is a difference between ME and 98SE? Loblo, does the patch work for you?
  20. schwups
    Is it necessary to patch the file in the driver and after that I have to install the driver with the patched file? Or is it needed to patch NVCORE.VXD in the system folder only? My first attempt to patch the system file failed. First test machine: NV 7800GT PCIE NV 7900GS PCIE, driver 82.69. It still hang during shutdown. I will try it on another machine soon. Last question: Could you write a patch for driver 82.16, too? Thanks
  21. schwups
    Yes, the modified graphics driver 82.69 supports the NV6600GT (shutdown problem). It should work. But I seem to remember, that there are little different versions of the 6600GT with different device ID's. Make sure, that your card is in the inf file of the driver. It's probably no problem. Some years ago I had a working 6600GT PCIE on WInME. I recommend to read the topic about the driver 82.69.
  22. schwups
    Bios settings: Ide Configuration > select [Compatible] for legacy OS or install RLoew's SATA Patch I've installed 98SE and ME on SATA and PATA disks, but never on a SSD. It was discussed here somewhrere on MSFN Windows 9x / ME. Chipset driver: http://windows98.xf.cz/chipset/intelinf.zip(manual installation) http://www.msfn.org/board/topic/163405-slipstreamable-intel-chipset-inf-drivers/ Graphics card driver (please note the shutdown problem and problems with more than 256MB graphics memory size): http://www.msfn.org/board/topic/97140-nvidia-drivers-8269/ USB driver NUSB: http://www.msfn.org/board/topic/43605-maximus-decim-native-usb-drivers/ official Realtek LAN PCIE driver 98SE/ME: http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=13&PFid=5&Level=5&Conn=4&DownTypeID=3&GetDown=false An audio driver for Realtek ALC 662 isn't available. Probably it is not entirely sure that all devices will work as desired.
  23. schwups
    Yes "GetAdaptersAddresses=t5". My IPHLPAPI.DLL version is 4.90.3000.0. Now I started ME with the original Kstub822. I only added [iPHLPAPI.DLL] GetAdaptersAddresses=t5 and [Kernel32.dll] GetSystemWow64DirectoryW=z2e120 The Browsers don't crash on you tube.
  24. schwups
    I get no crashes with Opera 10.6, 11.64, 12.02, FF 9.01, 3.5.19, 2.0.0.20, PaleMoon 3.6.32 and also Seamonkey 2.0.14 portable so far.
  25. schwups
    Of course not. "iphlpapi4" works with the IPHLPAPI.DLL of 98SE. But I made no further tests. I don't saw any advantages compared to [iPHLPAPI.DLL] GetAdaptersAddresses=t5 for me. I decided to wait for version 5, because 4.90.3001.2 could be good for 98SE and ME. Thank you for all the work you are doing!
×
×
  • Create New...