Jump to content
MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. ×

Goodmaneuver

Gold Sponsor
  • Posts

    748
  • Joined

  • Last visited

  • Days Won

    1
  • Donations

    $0.00 
  • Country

    Australia

Goodmaneuver last won the day on April 6 2020

Goodmaneuver had the most liked content!

About Goodmaneuver

Profile Information

  • OS
    ME

Recent Profile Visitors

3,598 profile views

Goodmaneuver's Achievements

51

Reputation

  1. If this is a new message after replacement of DbgHelp from wow64 into the applications folder then it could be a 32bit app. So you need both a 64bit DbgHelp and a 32bit version of DbgHelp I would think but not sure. Even though you have tried a different version of DbgHelp sometimes the app comes with its own DbgHelp which can be too old to interact with other OS components and I would try a different version again. For example Dungeon Siege 1 comes with DbgHelp and originally my WinME system had to use this version with the game. Now my ME system does not work with the Dungeon Siege 1 original DbgHelp and I have to remove it from the apps folder and use/rely on my system DbgHelp which is version 6.9.3.113. I use this version because it has more functions available over any newer version that is compatible with WinME. I think from memory that DbgHelp, ImageHlp and ImgUtil, to which I use LH5270 versions of the latter have to be compatible to each other. Use Dependency Walker to see if it is 64bit or 32bit.
  2. First it depends on what you mean by sleep. Sleep means that the machine can be woken up by pressing the appropriate key board key for example which can be set up in BIOS. Those startup settings really just mimic safe mode as far as I know. Safe mode does not load the hardware software drivers and runs hardware off BIOS. Most problems occur when a monitor is installed on a Standard PCI graphics adapter driver then the nVidia drivers are installed afterwards. First install a Standard PCI graphics adapter and then reboot. When system reboots do not allow a monitor to be installed, this is the important part. Now install the nVidia driver and then reboot. If your monitor goes blank or says "not supported" on reboot, go into safe mode and right click properties and choose the display settings of 640x480 @ 4bit color. This is the same as safe mode. Then when rebooted do not allow the monitor to be installed just yet, : - important. Change settings to 256 bit color and 800x600 or what you want, there will not be many choices. It will ask for a reboot most likely, so reboot. The nVidia driver after 256 color is running it will run the nVidia other software and now it is safe to the install the monitor driver. You may wait till 32 bit color is running first though then reboot and allow the monitor installation.
  3. I have Kstub823 loaded with Vista screen savers like Branded, MPREXE.exe, KMPlayer 4.06, PotPlayer 1.545995, VLC 3 & 2, MPC-HC 1.4.2499 and probably others, Ktree shows the APIs that are in Kstub823 but I wanted to know the APIs that are in use by the programs that are loading Kstub823. The Vista screen savers will not work without my Kstub823.ini. In a normal window the text lines can be highlighted with left click/slide then Control plus C for copy, if this can be done in Ktree then it could make it easier to work with. If IsValidProgramGroup and IsValidLocaleName both return a Boolean then it might work. See picture for the IsValidProgramGroup showing KexBases and Kernel32 with DW. I have been wanting the ResolveDelayLoadedAPI solution for a long time, we are nearly there to be able to use most windows modules that are in use and ResolveDelayLoadedAPI will be necessary to resolve this. If we use KernelEx KnownDlls and KernelEx Subfolders without the system mapping the location then it makes KernelEx conditional and complicated. I have shied away from this idea. I have spent most of my time recently on updating hardware. Objective is to update to a 4.2GHz + processor and I will update your Roll Call 2021 https://msfn.org/board/topic/182230-roll-call-2021/?do=findComment&comment=1193596 with all the details when completed successfully with each board, time willing. The modules I wanted to use were not kept but for a few, Oleacchooks, Dsparse, D3d10level9, WmpDui. I have WMP10 working and 11 could work too with ResolveDelayLoadedAPI. With more modules able to load then more applications will work. Nvidia device properties defaults to DX8 when the graphics card is unknown. Even though the picture says G73 it still does not know the video cards name it should be 7300 GT. The 82.69 drivers should display this correctly. I think I have a hangover from the older drivers and the registry will need cleaning and driver reinstalled.
  4. IsValidLanguageGroup is stubbed in KexBases when it does not need to be. I was going to try IsValidLanguageGroup function substituted for IsValidLocaleName in Dwrite but cannot as it is stubbed. We have had a stub for DelayLoadFailureHook for a long time but is it possible to get one for ResolveDelayLoadedAPI as this function call is used along side DelayLoadFailureHook in a many modules. Is there any chance that the functions in use by KexStubs be determined with Ktree? This could be used to trim down KexStubs.
  5. Thank you for backing me up on this Schwups, it means a lot. I like 10 as it gives the entry points of the module and I think it would be a good idea if we can redirect back to KexBases for example to use a stub again in a new defined module. I do not think it works though and memory locations can/will change. With the pictures uploaded the system fonts that are in use in that case are Arial western size 10 for all except Menu and Selected Items which use Verdana Western 11. So the default window font should be Arial western 10.
  6. The font size does not change with Ktree10 and has always been this way for me on all builds. You can see the square + size that the window metrics is working on Ktree9 and the window title bar font is the same for both. What could be different? There were no font changes, I have launched Ktree9 and Ktree10 both are running at the same time. What do you mean by Ktree9 and Ktree10 use different fonts? Ktree10 does not use my system window font: Ktree9 does.
  7. Ktree9h and Ktree9 obey the window metrics where as Ktree10 does not. This is the difference at resolution 2560x1440 : - using font size 139%. Picture is of Ktree9h 4.5.2 with no kstubs.
  8. 81.89 and 82.16 NVopenGL give similar results to 82.69 when just swapped into the system with the rest of the 82.69 driver left in place. See picture on page 20. NVopenGL is loaded in RAM by the diagnosis program. 77.72 NVIDIA did not show by the diagnosis program, it must have showed results for Microsoft OpenGL32 even though NVopenGL was loaded. So 1.1 was only shown as supported with 12% of vs 1.2. Function calls are appropriate for plugin compatibility for example but not solely a determining factor for the functioning of the DLL.
  9. You need to accept the rather large green rectangle at first time visiting the site then it does not need to be accepted again as it does not appear after that. All writing will be in German I believe. I downloaded it twice using FF52.9 on Vista.
  10. It was just a thought but if you are interested I think MakeHumane will need Python installed. Python from the Python web site, choose 2.7.1 https://www.python.org/downloads/release/python-271/ which is the latest one which will install from the MSI. Choose Windows X86 MSI Installer. Then you copy over the files from another installation like XP x86 do not forget Python2.7.dll which will be in System32 and goes in the ME system folder and replace the one in the MakeHumane folder too. I have copied over 2.7.13 but I think the latest 2.7 should work too which is 2.7.18. Apart from that it will need Win2K KernelEx setting and USP10 and I have a later Glu32 than ME original, it might be OK though. I have Blender on BASE setting and it works with menus working but it is not easily learnt and can give a NVopenGl exit error but does exit properly. I have registry config *\NV*.DLL as BASENOHEAP KernelEx setting. The no displaying the Humane character is the video card, Quadro FX5500, it is the only thing that did not work properly yet worked when I swapped monitors as described. Image upload of blender upper right corner with mouse point over the down arrow and top menu item 3D view.
  11. I have presorted it now with all errors fixed, hopefully. The Kstub823.ini is now running right on the limit and if I add another line then KernelEx stops running. I have made it easy for myself and added APPHELP.DLL definition functions redirect from bottom function names up alphabetically sorted till KernelEx stops. APPHELP is file vs 1.1.2599.4 BWC product vs 5.1.2600.5513. SDBAPI is WinME native. Kstub823_1.zip
  12. I have to say that OpenGL 2.01 did not show up as such after removing all NVIDIA files from the system and installing 77.72, it only showed 1.1. After installing 82.16 I got OpenGl 1.1 still and then when installing back over 82.69 back to 82.16 I got 2.01. The 82.16 is the same size as 81.98 and looks similar but definitely not the same. Now either 81.98 and 82.16 are of OpenGl 2.01 standard or only 82.69 is. More checks about it need to be done. I got the Human character to display by hot swapping the monitor then rebooting. There were no exit problems at all but I cannot now get the character to display again, did not hot swap again though.
  13. Did they help? If the message did not bounce then keep trying. We will miss you and you will miss one of your keen interests, so dial the emergency help line now and get help.
  14. It will be supported up to 66% of OpenGL 2.1 extensions though with 82.18 and 82.69. If there is a bad NVopenGL exit problem the program can be left in memory and cannot be terminated as NVopenGL did not release from memory when the program tried to detach (DW terminology). Otherwise there seems a delayed exit and there are no symptoms shown like your instance and the program exits. As well as what Jumper wanted, see if Firefox is still running with Starter or Process Explorer. My take on the NVopenGL is that the cube is very minimalistic and the exit problem could be a hardware issue. It seems NVopenGL needs exercising more. You could try Blender 2.64 or Make Human 1.02 etcetera to see if there is problems with exit there as well. One build of mine does not even display the Human and others work. Blender causes a NVopenGL exit error on that same build and another build does not have any exit trouble at all from Blender but has a python error on starting Make Human 1.02. It is the first time that I encountered a nondisplaying Human although with a non 2.0 card it can be non textured - white. (I am using a newly acquired video card as well as a different PCI SCSI card just recently changed but I think I can rule this out now because of the other builds characteristics).
  15. I thought I had sorted it. Please say if I did it wrong. Thought thought wrong, I forgot to sort some definitions or more likely did not save it to the correct location which also meant the .DLL suffix from 19 entries were not done which would free up some more characters. It would be still nice to know if the MSVCRJ.DLL entries were sorted correctly as it was sorted and it is the most complex. There were some other errors, you need a keen eye so I thought best to update it again now to fix the sorting and errors. I might append to the zip file in time. The original size is 4.6kB. I could not test all redirects but majority are straight forward. The main one of concern is the NtCurrentTeb one as I could not find the Microsoft document page for the NlsMbOemCodePageTag and relied on my memory and it is not proven and is wrong from what I understand now. For reference purposes the NtCurrentTeb routine returns a pointer to the Thread Environment Block (TEB) of the current thread. I have removed it from the zip and the OEM code page tag could be language specific 1252 for western European. My OEM Code Page is 437. https://undocumented.ntinternals.net/index.html?page=UserMode%2FUndocumented Functions%2FNT Objects%2FThread%2FNtCurrentTeb.html has a Certificate error but is an interesting site about the functions. The IPHLPAPI.DLL ones do register fast. I do know of a module that did not register when it should have. the registration stalled. You may not like it but I think it is NtClose that caused it to lock. I have registered some with all function calls known that do register then tried registering a module where the only unknown was the addition of NtClose in an implicit linked DLL and the registration locked up. I know that registering is not the full test but it is a good start.

×
×
  • Create New...