Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

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. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


roytam1

Backporting newer browsers to Win9X with KernelEx

Recommended Posts

DMA buffer affects all I/O operations which includes the video buffer. The settings are just a guide and are what I am using to give improved performance. System.ini will over-write the device manager reserve DMA buffer setting and visa versa so do not re-tick the 64k box. There was a diminishing improvement return on the video when going above about 50MB. You can use 44000 max file cache if you want but I have no trouble with 512000, 16384 will be too small other members have suggested a maximum of 132MB. On winME installation of ram has to be<2GB, that means 128k less will work. I have 1.5GB installed on this machine.  X-Setup Pro will show the buffer size which the system is using and what they say is not fully correct as I have explained. If members are interested in X-Setup Pro some settings are deadly so back-up beforehand. (CPU boost works)

Share this post


Link to post
Share on other sites

19 hours ago, Goodmaneuver said:

DMA buffer affects all I/O operations which includes the video buffer. The settings are just a guide and are what I am using to give improved performance. System.ini will over-write the device manager reserve DMA buffer setting and visa versa so do not re-tick the 64k box. There was a diminishing improvement return on the video when going above about 50MB. You can use 44000 max file cache if you want but I have no trouble with 512000, 16384 will be too small other members have suggested a maximum of 132MB. On winME installation of ram has to be<2GB, that means 128k less will work. I have 1.5GB installed on this machine.  X-Setup Pro will show the buffer size which the system is using and what they say is not fully correct as I have explained. If members are interested in X-Setup Pro some settings are deadly so back-up beforehand. (CPU boost works)

interesting, i wish i had this information earlier, although i still do not understand a lot of things, for the device manager part, do i still need to initially set it to 64k or can i just edit the system.ini and it should take care of the DMA aspect from there, but i would still need to manually enable dma on the storage device?, ( although unofficial service pack 3.64 automatically enables DMA on storage devices too ). 

is there a particular reason why past 50 MB or so, there are diminishing returns? diminishing returns as in, you don't gain AS much benefit but still there is some benefit? can you also explain to me what the pagebuffers means? how do i know what is the best setting. maxphyspage and minfilecache and maxfilecache are straightforward, however i am not understanding these other modifications. also the site below lists 1-256 as a range for the dma value, is this just a random range they put, because 256 would only be 256 kilobytes, less than one MB only, or am i calculating it wrong? 

i also noticed a 32 bit setting, i forgot exactly where i got the info and / or what it does and where you put it, are you aware of this setting?

http://smallvoid.com/article/win9x-16-bit-dma.html

so i researched more and noticed a source saying the dma buffers for windows 95 should be less than 16 MB, does this apply to windows 98 too? my question altogether is are there any compatibility problems with having more than the 64KB setting from device manager and / or what would be the best setting in system.ini that wouldn't cause compatibility issues and would operate the "fastest", also factoring in that "32 bit setting". i don't want to use any "tweaks" that would be detrimental or cause compatibility issues. i use those specific vcache and maxphyspage settings in my builds because that's the most reliable way that seems to work i suppose. 

https://www.dell.com/community/Desktops-General-Read-Only/I-O-subsystem-error/td-p/319016

Edited by cov3rt

Share this post


Link to post
Share on other sites

@cov3rt,The tick in DM will still be ticked. If you re-tick the DM driver settings 64k box it writes over the system.ini DMABufferSize=2048 to DMABufferSize=64. You can run with 64k size buffers if you want, make PageBuffers=700 and the total DMA size will be similar to the setting I suggested. When viewing video at high monitor resolutions the up sizing of the DMA buffer is necessary to improve frame-rate on browsers, they may not have GPU memory employed for the resizing of the output. Yes diminishing gains thats all, remember it is only 50MB so no trouble allocating memory. PageBuffer is RAM memory working space and PageFile is HDD memory working space both controlled by the virtual memory manager. DMA buffer size affects all I/O, storage devices included. You can choose Double Buffering (double the size) for storage devices in MSDOS.sys DoubleBuffer=1, which I run as I have SCSI for more speed. Yes 256 is 256kB, X-Setup Pro says a range up to 64kB so discrepancy. Trial and error are my settings. The memory allocations that are affected are controlled by vmm32.vxd I think and vmm32.vxd will be different between OSs but 16 bit should be able to allocate up to 2GB of total memory. The answer is for the bottom short cut given is for a general non startup problem where there is a full buffer. The Win95 in question is different to my WinME if it using ios.vxd and vcache.vxd as I am not using them. What the member is asking is how to remove the program, all VXDs auto start that are in the system IOSUBSYS folder I think (check bootlog.txt), so removing the offending VXD would help and VXDs are not always compatible between the OSs.

You can change the ThreadingModel from Apartment to Both right throughout the registry, appears to have no ill effects and can speed up performance especially when there are many modules on single thread. Edit from top to bottom with 9x systems. Make sure a "match whole word only" approach is taken when using a text editor and just edit Classes let the system up date the Local Machine settings otherwise a registry corruption may occur.

My system.ini settings that may have a performance influence including vCache *WinME*. Conservative swap file usage is a disadvantage in my experience (creates problems).

Recently upped the settings to:

[386Enh]
ADIXctlLevel=1
ConservativeSwapFileUsage=0
Paging=on
PageBuffers=512
DMABufferSize=256
LocalLoadHigh=1

[MathCoprocessor]
FPUFlags=1


[vCache]
MaxFileCache=512000

Edited by Goodmaneuver
settings change

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...