SweetLow Posted February 7 Posted February 7 (edited) 16 hours ago, defuser said: CREGFIX.COM + EMM386.EXE Two solution exist - or make driver (.SYS version) and run it before EMM386 or make DPMI version of CREGFIX. P.S. http://sweetlow.orgfree.com/download/cregfix.zip .SYS version for test Edited February 7 by SweetLow 1
defuser Posted February 7 Posted February 7 2 hours ago, SweetLow said: Two solution exist - or make driver (.SYS version) and run it before EMM386 or make DPMI version of CREGFIX. P.S. http://sweetlow.orgfree.com/download/cregfix.zip .SYS version for test Checked it out. If you run this CREGFIX.SYS after EMM386.EXE in CONFIG.SYS - the above error occurs. But if you put it BEFORE it, there is no such error.
SweetLow Posted February 7 Posted February 7 It is only half of test. Do Windows load successfully after that?
SweetLow Posted February 7 Posted February 7 50 minutes ago, MERCURY127 said: why dont make combo version as one exe file? 2 hours ago, SweetLow said: version for test N.B. And probably you can just do such version youself if you need it: COPY /B CREGFIX.EXE+CREGFIX.SYS CREGFIX.EXE, isn't it?
defuser Posted February 7 Posted February 7 15 minutes ago, SweetLow said: It is only half of test. Do Windows load successfully after that? On the current hardware (Without VCACHE error) - loaded successfully. For reliability, it would be necessary to check this on the problem hardware (Which is subject to this error), but I don't have it at hand at the moment.
SweetLow Posted February 7 Posted February 7 Just now, defuser said: I don't have it at hand at the moment. And why did you ask solution without having problem?
defuser Posted February 7 Posted February 7 55 minutes ago, SweetLow said: And why did you ask solution without having problem? I'm focusing on choosing the right hardware for the new configuration, and I came to ask if there is a solution to this problem. The choice depends on it. If there is a solution, then it will be one piece of hardware (later). And if there is no solution, then it will be a completely different hardware (earlier). Such things you want to know in advance, so as not to make a mistake and make the right choice.
MERCURY127 Posted February 7 Posted February 7 1 hour ago, SweetLow said: COPY /B CREGFIX.EXE+CREGFIX.SYS CREGFIX.EXE, isn't it? no, no, no! hybrid sys+exe is not just concatenation. when loading exe file via DEVICE= command, DOS wiill skip exe header only, not all body of exe file. u need rewrite source for it.
SweetLow Posted February 7 Posted February 7 1 hour ago, defuser said: and make the right choice It is good logic, but this problem now is minor for systems with this bug. 1 hour ago, MERCURY127 said: u need rewrite source for it. Ok, but i think it is not so simple for DPMI executables at all.
MERCURY127 Posted February 7 Posted February 7 3 hours ago, SweetLow said: it is not so simple for DPMI executables why even use dpmi for such simple app?
SweetLow Posted February 8 Posted February 8 19 hours ago, MERCURY127 said: why even use dpmi for such simple app? I assume just because it is relatively easy way to deal with PM environment.
SweetLow Posted February 8 Posted February 8 (edited) On 2/7/2025 at 10:17 AM, SweetLow said: or make DPMI version of CREGFIX http://sweetlow.orgfree.com/download/cregfix.zip For test: Added WP_OFF.EXE and as it is PM application it clears CR0.WP (Write Protect) bit only. Works with Ring 0 DPMI hosts only - as included CWSDPMI R5 and R7 versions. Edited February 8 by SweetLow
SweetLow Posted February 15 Posted February 15 Release: https://github.com/LordOfMice/Tools/blob/master/cregfix.zip Added .SYS and DPMI versions 1
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now