defuser

It's clear. It turns out that there are several possible scenarios at once. Older vBIOS can understand PTB EDID values, such as those that correspond exclusively to GTF. But don't quite understand CVT, CVT-RB and CVT-RBv2 (Specified in the EDID for DVI \ HDMI of a modern monitor). Therefore, the BIOS chooses something from the standard values when it suddenly encounters an unfamiliar "CVT", and even at 16:9. Hence, 1024x768 (apparently GTF) is forced. Another option is that 1024x768 can simultaneously be a certain " vBIOS Default "and it is always reset to it when it cannot set the requested"CVT". This can be easily checked, but you will need to modify the EDID again. Replacing 1600x900_CVT with something not quite standard, something like 800x600_GTF. The old vBIOS should understand this if it really accesses this block (PTB). And instead of 1024x768 at the input, if everything is really so, it should immediately become 800x600. Otherwise, this mechanism does not work at all in NV34 (not implemented yet\Disabled by default\Disabled for this particular monitor\Works differently than expected). Well, accordingly, the resulting option may be just the same in the fact that the old vBIOS may not read this block at all and just choose something from the standard values at once. But then again, why is only one single value always used? There are also a lot of them (There is, by the way, and 1280x1024@75hz, why not choose it, for example?). Judging by this behavior, it seems to me that it still uses internal values from vBIOS (Choosing only one of them). And what it starts from then, choosing this "only correct" value, if not from EDID, remains a mystery. I also looked a little bit at UniVBE on NV34 (So far only superficially, it is quite buggy and it has two different recommended versions, the behavior of which is slightly different, as well as their glitches. Therefore, all the following observations are only preliminary). With DVI allows you to still change the frequency up to 75hz at 1024x768, but only if the game itself is selected exactly 1024x768. When you select any other modes, the input to the monitor remains as before 1024x768@60hz. Also such an option. It's just a coincidence that the game has such a display mode. Some games can't even exceed 800x600_Vesa2 (or even even less), which means they're all out of whack? Well, the limit of 75hz is clearly not hardware. But on the G70, of course, this does not work at all, because the game does not support 1920x1080 or even 1600x900 (Which UniVBE or vBIOS chooses). Accordingly, it cannot be selected in the game. And if you wind up even just 60HZ at the same 1024x768 or 800x600 and select it in the game, it immediately writes that there is no signal (That is, it tries to do something there, but it clearly breaks off about something and flies out of the range). I will dig up this effect in more detail. Notably, UniVBE itself acts similarly to VBIOS in both cases, setting hard-coded 1024x768 for NV34 and 1920x1080\1600x900 (depending on the EDID) for G70. That is, it does not bring anything new in this regard. Presumably, if you set EDID 1024x768 as preferred (PTB), then the G70 will be able to work similarly to NV34. But this solution, again, is not perfect, for the same reasons. Along the way, I also managed to find out that data from the EDID is read every time the video mode is changed in the game. Thus, on the fly, in principle, it would be possible to change the preferred mode and refresh rate so that the video card would actually use it. But this requires a powerful software tool that allows you to modify EDID data on the fly (something like "EDID override for DOS"). Or a deep revision of UniVBE could also be a good solution to quite a few similar problems, because, among other things, it also added new modes to the game (Which were not originally available), and also includes support for VBE 3.0 (Where it is not yet\no longer yet), although it actually turns on not everywhere (at least as far as the refresh rate is concerned) and usually doesn't work on anything higher than NV3x (at least on VGA. On DVI, as you can see, too, a positive result has not yet been achieved). I also checked "Aspect". The actual aspect ratio (If measured with a measuring tape) of the 1024x768 video mode under DOS, embedded in 1600x900 (Which the video card outputs) and applied to it by the "Aspect" monitor, is 4:3 (400x300 millimeters physically). Of course, when in Windows, in the same framework, the size of 400x300 millimeters, 1600x900 remains embedded - this does not look natural. But this can be easily corrected even in several possible ways (by setting the video driver zoom, changing the refresh rate to a different one than used under DOS, or by setting the monitor itself). So this is just not a serious problem here (Just an annoying flaw).

A small correction. I just checked the whole thing again and no, it really goes out fine in DOS. It's just that for some reason the USB keyboard doesn't work there and therefore nothing can be done. It looks like a hang, but in fact it is not a hang. You can add the program to DOSSTART.BAT and it will run successfully after exiting DOS. It seems to me that the USB driver captures the keyboard under Windows and does not want to give back control of the CSM (Which works before Windows starts). Something like that. However, this is more than enough to perform the specified check. I set the monitor zoom mode in the driver (the third option), added Quake to DOSSTART. BAT, and exited in DOS. Quake started. But the input of the monitor still receives 1600x900@72hz (Registered by me in the EDID, at the moment, in the "Preferred Timing Block" section). The same mode is applied to the monitor both in pure MS-DOS 6.22 and in the DOS window of Windows 98. Regardless of what is installed on the desktop. And by the way, the" wrong " proportions (Typical for 4: 3, stretched by 16:9) they are saved for this mode and only for it (If you specify a different one in the EDID, it will be different). Apparently, due to the fact that at an early stage of loading, the monitor ALREADY works with this video mode and applies this "wrong" scaling to the "correct" video modes of early DOS embedded in it, and this is apparently remembered somewhere. They've made a lot of sense out there... Just as planned, I checked the NV34 again and compared it with what the G70 has. The first value is what is selected in the game; the second value is what actually goes to the monitor input. "Aspect" - indicates that there is an active option to enable aspect ratio support in the monitor menu. Underlined - playable modes (No lags. Frame synchronization works). In all cases - UniRefresh set to 72hz; Quake 1; MTRR LFB WC. VGA NV34: 320x200 => 720x400@70 360x200 => 720x400@70 320x240 => 848x480@72 Aspect 360x240 => 640x480@60 Aspect 320x350 => 640x350@70 360x350 => 640x350@70 320x400 => Out of range 360x400 => 720x400@70 320x480 => 640x480@60 Aspect 360x480 => 640x480@60 Aspect 640x400 => Out of range 640x480 => 848x480@72 Aspect 800x600 => 800x600@72 Aspect 1024x768 => 1024x768@72 Aspect 1280x1024 => 1280x1024@72 Aspect VGA G70: all the same, except: 320x240 => 640x480@60 Aspect 320x400 => 720x400@70 640x400 => 720x400@70 640x480 => 640x480@60 Aspect 800x600 => 800x600@60 Aspect 1024x768 => 1024x768@60 Aspect 1280x1024 => 1280x1024@60 Aspect DVI: NV34 (Default EDID) - all modes (except 1280) => 1024x768@60hz Aspect NV34 (Modified EDID) - all modes (except 1280) => 1024x768@60hz Aspect G70 (Default EDID) - all modes => 1920x1080@60hz G70 (Modified EDID) - all modes (except 1280) => 1600x900@72hz Aspect As for the "Aspect" mode, in fact, with it, the standard 4:3 modes stretched at 16:9 seem to look, oddly enough, approximately correct. But NV34 in DVI, for some reason, not only ignores UniRefresh, but also what the monitor itself requires from it. Perhaps this is just the case when the value is hardcoded in the BIOS (Apparently, ATI does about the same), or it takes this value from some alternative location.

At the moment, I can change the update rate under DOS via DVI connection in only one way - by changing the EDID and flashing it to the monitor. But this method does not seem ideal to me, for the simple reason that it is somewhat tedious to flash the EDID for each DOS program that needs its own frequency. Isn't there a simpler, programmatic way for DOS to change the frequency in any way (Programmatically redefining the EDID under DOS would be a perfectly suitable solution if it existed). By the way, are there any tools for flashing the monitor's EDID under DOS that use the i2c bus and support 256-byte EDID images?

It thus scales 1600x900 under DOS (And in the DOS window of Windows), in the case when it is entered in the standard 4:3 (For example, 1024x768). And after completing the full-screen DOS application and returning to Windows, these "incorrect" proportions are preserved for 1600x900 installed on the desktop (Texts and shortcuts are narrowed, and black bars remain at the edges). At the same time, from a "clean slate" under Windows, the monitor does not allow you to set the "Aspect" mode (Other options are available besides this). For this zoom mode to become available again, something must be written in 1600x900 under DOS. It looks very confusing. Most likely, this still corresponds to some interaction specification. Somehow, the monitor under DOS determines the parameters and the ratio of the entered resolution. But this is not the right behavior. It is necessary that the video card outputs, for example, 800x600, as it is (As it is selected in the application), as it happens with a VGA connection. UniRefresh + Quake 1. What other apps can I try for this purpose? The output in DOS does not work for me (It exits and freezes). Only a separate MS-DOS 6.22 (Multiboot menu of Windows 98) works, in which I test all this. The DOS window also works under Windows 98 (Also used). Running DOS received with "BootGui=0". As well as DOS, located on the OEM CD of Windows 98. Everywhere the picture is almost identical. The scaling settings, in turn, apply to the DOS window of Windows 98. But only the first two options work (Enter in the center or Stretch). The third option (Passing native permission) doesn't work. For pure MS-DOS 6.22, the tool mentioned above (In the sixth message) is used: http://rayer.g6.cz/programm/nvsc.zip It also allows you to use only the first two options (Fit or Stretch). At the same time, under any DOS, the above method of scaling the monitor is always used, determined by the entered resolution. The monitor input is always supplied with what is specified in the monitor's EDID (including the refresh rate). And so it happens. I try changing the refresh rate as usual using UniRefresh, but it doesn't work for DVI connectivity. Only for VGA (and even then, not on all VBE 3 compatible nVidia video cards).

VBE 3.0 support is generally available. But in the case of DVI, this is not enough. We need something else. Or something interferes with full-fledged work (What exactly?). This generally exists and works fine over a VGA connection. At least in combination with some VBE 3.0 compatible nVidia-based cards, such as NV30, NV31\NV34 (Only some vBIOS implementations actually allow this capability) , and NV38, from the ones I've tested. For the first three, the UniRefresh utility is suitable, and for NV38, the patched UniVBE is suitable. However, in none of these cases is it possible to change the refresh rate exactly when DVI is connected (Always remains 60hz). As for the G70, which I'm tormenting at the moment. Using a DVI connection under DOS, it always remains 60hz by default (Or another value that is explicitly specified in the monitor's EDID (In the Preferred Timing Block)). And it doesn't change to anything else with the help of these utilities. Alas! As specified in this EDID block, it remains under DOS in all cases (and in the DOS window of Windows 98, too). I should probably try switching back to NV34 (where VBE 3.0 is guaranteed to work via a VGA connection) and think carefully about why this doesn't happen with DVI... What else can I try to do? Here by the way there is a link to this: "Bit 11 Refresh rate control Select. If set to 1, use usеr specified CRTC values for refresh rate, otherwise use BIOS default refresh rate." Maybe somewhere you need to switch to 1 by hand? This is via RU.EXE is it changing or is it being changed in vBIOS? If the former, how do I get to this place? I would like to see what the G70 value is now.

I suggest, for the convenience of research, that for the time being we put out of brackets everything that concerns scaling (We will return to this if anything later). How do I resolve the issue with the refresh rate? Having decided at least for the beginning of this issue, you can move on. This is more important in the context of application compatibility. A simple example is that the game requires setting 72hz, instead of 60hz (by default), so that it works correctly under DOS. For another game, 75hz is good. What should I do if I connect DVI? What other options are there?

Moreover, even the monitor scales native 1600x900 approximately exactly as it is drawn on this preview, if you select "Aspect" in the settings of the monitor itself. Thanks, but it doesn't help.

Hi. The question is a bit different. For clarity, I will now try to explain first with an example of how this works in Windows. And then we can move back to DOS. So, in the nVidia settings, we have the ability to adjust the zoom (Different options), let's look at the first three of them: DVI connection. On the desktop, we now have 1600x900. - when you select the first option (Display adapter scaling), it turns out that the input to the monitor is actually 1920x1080 (1600x900 scaled by means of the video card to 1920x1080); - when you select the second option (Centered output), it turns out that the input to the monitor is actually 1920x1080 (1600x900 inscribed in 1920x1080 in the center, using the video card, with black stripes on the edges); - when you select the third option (Monitor Scaling), it turns out that the input to the monitor is actually 1600x900 (1600x900 as it is, scaled by the monitor's tools as set in the settings of the monitor itself). Now we go back to DOS and see at the input to the monitor 1920x1080@60Hz (The first or second option, depending on the settings in nvscaler). How do we get the third option here? What would be the input to the monitor actually served what the software requires? The second part of the question is how to change the screen refresh rate under DOS, with a DVI connection? For comparison, we connect via VGA, go to DOS and see-just the third option (Honest 720x400@70hz is fed to the monitor input). On DVI it is necessary as well that would be. How do I do this? Here's the question.

The monitor scales what the video card gives you. And if it gives 1600x900 (In which 800x600 is scaled, by means of the video card), then the monitor works with it as with 1600x900, offering options available for this resolution for further scaling (Emulation 17", 19", 4:3, for example, and so on). Nah, well, it's not like that at all... We may also want to change the refresh rate (and not just change the resolution\disable zooming). How will the monitor handle this? I didn't find anything about this for DVI (There are solutions for VGA, they are tested and work. Such as UniRefresh, UniVBE, VBEHZ), but for DVI, the frequency specified in the monitor's EDID (Preferred Timing Mode) is always used, at least for nVidia. I haven't found any utility that allows you to switch refresh rates (For DVI) yet. There is another idea here - to make several versions of EDID, prescribing in each your preferred video mode and refresh rate (So that you can choose your own for each case). But how to re-shoot EDID under DOS? Where is it actually stored in memory (so that it can be replaced and reinitialized)? Of course, outside the monitor. After all, it comes from the monitor to the computer and is stored somewhere in a volatile part of the memory. I will later try to test one hypothesis, whether it is even possible in principle to initialize (And force to use) another EDID in one day, without rebooting the PC (So far over the wire, with the actual transfer of another EDID). If the experiment is successful , the possibility of redefining the EDID under DOS in memory may theoretically exist (which is at least somewhat encouraging). PS: I have already found information about the existence of hardware solutions that allow you to replace the EDID. But for now, I would like to try to limit myself exclusively to software tools (After all, with VGA it is possible to do this. Why all of a sudden such difficulties with DVI?). ___________ Checked it out. And it really can work that way. Loading any compatible VBIOS image file under DOS (Using RamBios\VGABios) causes the video card to read the EDID in a new way (While RamBios\VGABios, along with the image, can be unloaded immediately after that, so as not to take up memory). It remains to find a way to replace the EDID data sent by the monitor with your own (custom) ones, and then you can load any custom EDID under DOS (With the necessary video modes and update frequencies). There are no other software solutions to the problem yet. Tested on GeForce PCX 5900 (PCI-E x16).

Yes, all these modes work fine (including VESA), but all of them are forcibly scaled by the video card to native under DOS, if connected via DVI. Via VGA, all modes (VESA, at least) are displayed "as is", as set by the software. I would like to do the same for DVI connection. Yes, that's right. When connecting an nVidia video card via DVI, from the moment the PC is turned on, the video mode specified in the monitor's EDID ("Detailed Data" -> "Preferred Timing Block") is set and what resolution and frequency are specified in this block, these will be used in the future under DOS (And in the DOS window of Windows 98, too). And all other modes that the DOS software requests are forcibly scaled to this previously set resolution (and frequency). What you need to specify in this EDID block will happen. When the video driver under Windows 98 is included in the game, other (Extended) EDID blocks (which can also contain other video modes) are also taken into account, which allows you to set custom permissions that the monitor can accept natively (As is), if they are listed in these blocks. Otherwise, you are forced to scale to the native video mode of the same or the nearest supported video mode specified in these extended EDID blocks. The highest resolution specified in these blocks (CEA Extension) is considered the native monitor resolution for the nVidia video driver under Windows 98. Here the question remains, why do DOS ignore the standard modes listed in the main EDID section ("Standard Data" - > "Established Timings" + "Standard Timings") and immediately switch to "Detailed Data"? This is also the most basic thing, and it should be taken into account first of all. I haven't checked yet, but I suspect that this may be due to the flag set under "Feature Support" -> "Preferred Timing Mode" (Preferred Timing Mode includes the Native Pixel Format and Preferred Refresh Rate of the Display Device). I'll have to try turning it off. PS: When creating this topic, I was just hoping that maybe someone knows some low-level DOS tool that allows: - adjust EDID data in memory. - manage the DVI connection in real time (changing, for example, the refresh rate). - enable / disable forced scaling by the video adapter. On the last point, there is indeed such a tool, but it works a little differently than expected. Namely, the video mode remains the same (For example, 1600x900), set according to the EDID at the start of the PC (As described above), only 800x600 scaled to it (For example) are obtained in the center or from the edge, instead of stretching (By default) completely. That's all the management. This is a bit different.

Greetings. Faced with a problem related to DVI connection. It appears both in pure MS-DOS 6.22 and in the DOS window of Windows 98. I used different nVidia graphics cards and everywhere the picture is almost identical. Namely, when I set any resolution and refresh rate (640x480; 800x600; 1024x768), it is reset to native for my monitor, determined by the EDID for the DVI port. Monitor, any selected input resolution defines as 1600x900@60hz. Naturally, I would like to put something else. For example, 800x600@72hz. but the input is still the same 1600x900@60hz. When I connect via VGA, everything works correctly. What resolution and frequency I set - this is displayed. As far as I understand, the nVidia video card scales any outgoing resolution to native, if connected via DVI. Is it possible to somehow disable forced scaling under DOS\9x for DVI connection or somehow explicitly set the required mode?

Yes, the Quadro FX 4500 (G70) works acceptably with 512MB of video memory on board, at least with ForceWare 77.72 drivers (and higher), but only after installing a special patch. For ForceWare 8X drivers.XX you will need the "PTCHNVSZ" package (By Rudolph R. Loew). With this package, you can fix the driver and/or the videobios so that it works correctly with this volume. It may also be necessary in other cases, as it contains several related fixes (FIXINTR, FIXEOI, Patch PCI.VxD) and other things that may be useful in some other cases (for more information, see MANUAL.TXT). For the most trouble-free 9x compatible ForceWare 77.72 driver, you can use a different patch (Created by analogy with "PCHNVSZ", but suitable for the 77.72 version of the driver): http://windows98.xf.cz/index.htm#NV7722PATCHED I use a combination of these two options - "FIXEOI" and "PATCHOPT" from the "PCHNVSZ" package + the corrected NVCORE.VxD (From the link above), together with the ForceWare 77.72 driver (The latest version with which D3D\DirectDraw still works without problems). And also nvOpenGl.DLL from version 71.84 (As newer ones caused problems in OpenGL). And MTRR correction (Without which the speed of some indicators in 2D and under DOS on PCI-E cards is extremely low). For G71 PCI-E, you will need at least ForceWare 8X. XX (With which there are a lot of still unresolved problems, in particular, with D3D\DDRAW). 77.72 doesn't have these issues yet.

Nothing is necessary, I already understood how to do it. Thanks for the tip. The reason is quite obvious - the name is long and the last letters of the name are still not visible: I just wanted to make the name a little shorter. RamDrive for example fits: I have only one RamDisk on the system, so it's hard to confuse anything.

Hello. Is there a standard way to assign a different default name? I changed the name several times in the disk properties, but it is not saved and each time from a cold start it is assigned the original one. Is it hardwired somewhere deep in the driver code? I tried changing everything I found in the registry, but also to no avail. Another question concerns access from DOS to a previously created disk under WINDOWS. Do you need a separate 16-bit client?

Quote from Readme: I checked and noticed the following. The contents of the RamDisk are preserved even after rebooting to XP and back. But if the PC is turned off (Even for a short time), the information is permanently deleted. That is, within the framework of a working session, you can safely make reboots, including rebooting in XP and returning back, and the information on the RamDisk remains. However, this does not work if RAMDRV4M is used on top of RAMDSK64 (which may be necessary if you need to copy something to RamDisk already at the DOS stage). It only works when using the pure RAMDRV4M variant. But it still works well. My checks showed complete data safety (based on the results of checking checksums) even after returning from WinXP. In XP itself, of course, PAE\PSE is disabled (Not used).

A very interesting decision. It seems that this is the first full-fledged PSE ramdisk in history that installs and works directly under WINDOWS! No more downloading of HIMEMEX (by Rudolph R. Loew). HIMEMEX itself, by the way, is not full-fledged: the PREALLOCATION function stated in the Readme does not work in it, as a result of which you have to use them together with BURNMEM (the first, in fact, for the RamDisk; the second for limiting memory). And, as it turned out during operation, the order in which they are launched (Together with HIMEM) in CONFIG.SYS is crucial. The most stable sequence turned out to be HIMEMEX > BURNMEM > HIMEM. This solved most of the problems associated with it. Now, thanks to RAMDRV4M, in the future it will be possible to completely exclude HIMEMEX from this scheme. But first you need to make sure that RAMDRV4M works as well, does not cause problems and is compatible with all the programs you use, and this will take time. Also, knowing a little history of the development of RAMDSK64 and its performance, depending on the newness of the hardware and, apparently, the BIOS version, the question also arises of the compatibility of RAMDRV4M with more promising hardware (In particular, based on LGA1700, in combination with the CREGFIX necessary there to fix VCACHE). It would be nice if someone (who already uses such hardware) checked this right away. I'm starting testing on HASWELL. And I’ll check the speed first: initial results with RAMDSK64: result with RAMDRV4M installed on top of RAMDSK64: clean result with RAMDRV4M: Amazing! Which, by the way, is quite remarkable, when I deleted the HIMEMEX boot line from CONFIG.SYS, rebooted and saw the drive letter "G:", instead of "M:", I expected to see it, of course, empty. As usually happens with RAMDSK64 after a reboot (If you don’t copy anything to it at the DOS stage or immediately after starting WINDOWS). But when I opened it, I was quite surprised: all the files and folders that were on the "M:" RamDisk before the reboot remained (On "G:")! Even the folder "CrystalDiskMark22_9x" was already there! It turns out that this data was stored somewhere during the reboot? But where? Is it really in RAM? I definitely didn’t have enough free space on the "C:" drive to store a backup of the appropriate size there. Simply fantastic. Well, okay, I will now test the pure version (Without RAMDSK64) under real conditions of use with regular programs. This may take a long time. Thank you. PS: How can I change the drive letter? I want to change it back to "M:", my software is copied when loading to "M:" and the shortcuts also lead to "M:" and all sorts of "TEMP", "Temporary Internet Files" are also registered there. I looked in the Readme and didn't see it. I opened the disk properties - there is a gray "G:" there. I understand that you need to install LetterAssigner? PSS: There was also a funny incident. When I installed it (Directly on top of RAMDSK64, without disconnecting the existing disk) - at first it seemed that the system was frozen (Everything froze and nothing could be done) and, after waiting a little, I was already reaching for the reboot button, when suddenly everything came to life and a message appeared on a blue background "Windows The volume that was removed had open files on it. Next time please check first to see if the volume can really be removed. Press any key to continue." Nevertheless, even in this situation, everything went well and the system continued to work normally after that, and the installed RAMDRV4M appeared in the device manager.

Yes, thank you, I tried it and this version really works well (Showing itself much better in some usage scenarios). However, there is a problem with Direct3D \ DirectDraw in the 8X.XX driver versions (including 82.69) still remain. NVOPENGL.DLL from version 82.16, it was not compatible with the 77.72 driver (Applications crash with the error "abnormal program termination").

Has anyone already tried to build a hybrid version of the driver that combines the advantages of version 77.72 and version 82.69? I tested version 82.69 some time ago and found good support for OpenGL 2.0.1, while Direct3D applications worked crookedly, ran slowly, or even crashed at startup (the same NFS2000 for example). DirectDraw performance also suffered. While version 77.72 lacks all these disadvantages, Direct3D\DirectDraw works fully, but OpenGL version 2.0.0 and its performance is lower. In addition, NVOPENGL.DLL most often, it was necessary to roll back to version 71.84, to achieve the greatest stability and compatibility, in combination with PCI-E cards. But this was already disliked by some new programs that require a newer OpenGL (From version 82.69). Based on all these observations, it is quite natural to build a single version of the driver based on 82.69, consisting of several versions, which will take into account and correct all these shortcomings. Or somehow fix Direct3D in 82.69. Has anyone already tried to do something like this, does it make sense to start it at all (Or none of this will work and everything has been tried for a long time)? What other general practical recommendations do you have for PCI-e GeForce 6\7 Series users today?

And yes, some later programs also use this path to place their data folders: C:\WINDOWS\Local Settings\Application Data\ Check just in case your program expects to see the necessary data in the folder located there.

If you like Internet Explorer 4.0 and don't want to update it (or don't want to radically update 98FE while maintaining the most original state), but you need an application compatibility level close to Windows 98 SE + KeX (With up-to-date experimental updates), providing support for, for example, VLC 2\3, Mypal29\FF52 and so on, you can install in a clean Windows 98 FE, at least Windows Installer (InstMsiA.exe), as well as DirectX 7 (Optional). You will only need to update the following system files:: At the same time, the functionality of IE4 is fully preserved. You can also install IE5\5.5 while maintaining IE4 (The system will have TWO browsers at the same time). This is a standard feature provided by Microsoft, eliminated starting with IE6 and higher. To do this, select the appropriate item in the IE 5.X installer: However, the first option seemed more life-saving to me. I use it myself. This is basic. The rest should be viewed locally (each specific program may have its own additional wishlist).

I see. If this is a really general problem and affects other relevant desktop solutions, it is probably not worth making changes until a full-fledged functional fix is found.

Thank you. I tried it. In Firefox 9, the CPU usage is 15-25%. In Opera 12.02, only 7-8%, after the video is fully loaded. Sometimes it takes a few seconds to load or doesn't fully load. In both cases, only HTML5 seems to be used. Switching to HD doesn't work. Opera also requires disguising itself as Firefox or opening the same page in Firefox in parallel (I can't imagine how this can be related, but there is a fact). It's not very stable. In Mypal 29, it works noticeably better and even switches to HD (But not everyone in this browser has sound, so it's less relevant). All that's missing is a button for explicitly switching to FlashPlayer, as well as adjusting the playback speed and quality selection. Otherwise good.

So everything is more or less clear. That is, with this option, the ability to write is saved and thus it works correctly. Questions are removed (This was not entirely obvious to me from the description). Thank you for this valuable clarification.

I have such a question: there in the source it says - " noticed that the cause of the page fault was a write to a non-writeable page while executing in ring 0.". What does it mean? Under "normal conditions", it should have made this recording successfully? What is this entry, how important is it, and what does it affect? Is it possible, instead of eliminating the symptoms, to allow the necessary recording to be performed (If my assumption is correct), by removing write protection to this location? What can be the concomitant consequences of the fact that this record cannot be executed? Even if my concerns are unfounded, I would still like to see a more detailed explanation - what and where it wants to write down, why it can't do it, and what indirect consequences it may have. For clarity, let's say if we take a computer based on 440BX or similar, fully 9x compatible, does this recording succeed there?

When I searched, I didn't find anything easier than LICEcap v1.1, which allows you to write to a regular GIF file with a given refresh rate. It is able to display the passage of time, as well as mouse button clicks: It works on Windows 98 and higher. Sometimes, however, it was still necessary to convert the resulting GIF to MP4 to add to the video hosting service. This was required in cases where the GIF size exceeded the size allowed for adding to the photo hosting site. There are quite a few free converters that allow you to do this, both directly in 9x and in a VM with a later OS, but I made do with free online services. Thank you, this tool really looks great, light, simple and convenient, I will definitely try it out in action.