Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won

  • Donations

    0.00 USD 
  • Country


Everything posted by deomsh

  1. I have only experience on Windows 3.1 (so NOT WFW 3.11). Browsers: best is Netscape 4.03 or 4.04, using a proxy server or a webproxy. Without: Netscape 3.04. Watch a-synchronous DNS. More details here (go to page 2): https://web.archive.org/web/20180329130629/http://win3x.conforums.com/index.cgi?board=net&action=display&num=1517876379
  2. Can't help you as such, but just for the record: did you install DirectX 9.0c (win9x version)?
  3. All right, if you are fine with your speakers, than stay with HDAICOUT.HDA.000 Apparently your laptop uses other Pin(output)Widgets than I selected: 0B, 0E (with HP-amp) and 10 (mono-out). To find the right ones will need quite lengthy experimentation using Get-commands...
  4. All right, lets try this version of a tailor-made HDAICOUT.HDA first. Following steps: 1) Rename current working HDAICOUT.HDA to HDAICOUT.OK1 2) Rename new version and reboot, check if everything is working as before (VolumeWidget=$13 !). 3) Set VolumeWidget=$1C in HDACFG.INI and test if WAVEOUT.EXE is ruling speaker-volume only. Hdaicout.hda.Dell_Latitude_6430u
  5. Good, so you can use this instead of WAVEOUT.EXE. Are you interested in my idea to redirect the speaker signal line to the Mixer_1C, so you can use WAVEOUT.EXE to rule the speaker-volume independent from your headphone?
  6. Fine. There is no hurry, take all the time you need. Next: if you play an audio-file in MediaPlayer, is the volume slider of the player working?
  7. That's good to know, if I am right this means Mixer_1C is not in the playback signal path. Sad, but is reported earlier. No driver is needed! Direct Sound is part of DirectX. Check with Start > Run > Dxdiag which version is installed. Best is DirectX 9.0c (Win98SE compatible version). If I am right MPlayer uses DirectSound by default. In some players you can choose output device, in case of HDA2.DLL you should choose DirectSound: HDA Sound (title is set by the driver!). Maybe possible in MultiMediaDevices too (option for Playback).
  8. Great. If you read carefully the link I provided, you will see WAVEOUT.EXE is not always needed, except for System Sounds (but these can be disabled) and Soundplayer (don't remember the exact name). The trick is to use the volume slider of your player, if the player can be set to DirectSound: HDA Sound (or if the player uses this setting already by default). Is VolumeWidget=$1C working too? I ask because I have an idea to let WAVEOUT.EXE rule your speaker volume, while your headphones will get maximal volume, modified by the volume slider of a player/ and or the physical volume slider on the headphone (if your headphone has any). BTW how behaves the sound switches on your keyboard?
  9. Thanks. Let's first try to fix WAVEOUT.EXE. According to the data-sheet, WDGET-diagram on page 50, there are three volume-widgets in the playback path. For DAC0 widget 13, for DAC1 widget 14 and the mixer has widget 1C. WAVEOUT.EXE is dependent on the VolumeWidget setting in HDACFG.INI. Default is $14, so try first VolumeWidget=$13 and later VolumeWidget=$1C too. More information about volume & HDA2.DLL: https://msfn.org/board/topic/178295-audio-driver-for-realtek-hd-audio-hardware-testing-thread/?do=findComment&comment=1161770
  10. Be aware copying can be slow with the vcache-solution. SMARTDRV.EXE can help, best is (in AUTOEXEC.BAT): SMARTDRV.EXE /X /L /V /B:57344 Did you try WAVEOUT.EXE already? Start > Run > WAVEOUT.EXE With help of your HDACFG.INI I found out your codec is IDT 92HD93, revision 100203. Can you search for the data-sheet so I can take a look... BTW Do not upload because of copyright, just the web-address (mostly '.pdf'}
  11. Thanks a lot! About the jittery/halt: did you already try higher values of MinTimeSlice? Default is '20', (my experimental) max is '100'. So try 'max' first in SYSTEM.INI, [386Enh] MinTimeSlice=100
  12. So, that's quick, congratulations Will you do me a favor and upload HDACFG.INI and HDAICIN.TXT, so I can see which HDA-Controler and which HDA-codec is used on your system and which responces the HDA-codec gives to my version of HDAICOUT.HDA (000)? BTW: are you still using version 'J' of HDA2.DLL? I just found out latest version is 'L'. I will test soon...
  13. The instructions on Operating System Revival are correct for WinME only. In case of Win98SE use for manual installation (taken from Operating System Revival + corrections): Instructions (Windows 95/98): 1. Download Watlers' driver HDADRV9J.zip 2. Place HDA2.DLL in C:\WINDOWS\System 3. Make sure HDARSR.EXE HDATSR.EXE and WAVEOUT.EXE are accessible (place in "C:\WINDOWS\SYSTEM" for convenience) 5. Add line "HDATSR.EXE" to AUTOEXEC.BAT (without quotes) 6. Add to SYSTEM.INI,[Drivers] "WAVEHDA=HDA2.DLL" (without quotes) 7. Reboot If there is no sound, try my quasi-universal version of HDAICOUT.HDA (found in DaveH's tread) and place in C:\WINDOWS\SYSTEM and reboot. If there is sound but system is unstable try in SYSTEM.INI, [Vcache] MinFileCache=1024 MaxFileCache=1024 + you can speed-up your system by adding line "SMARTDRV.EXE" to AUTOEXEC.BAT (without quotes). Always reboot in between. If there is still no sound, ask @deomsh for further help (only if you are fully dedicated to a long project, and willing to follow instructions you probably will not understand).
  14. Your source says: 'To warn Windows that you have more than 512MB of memory installed, add the following line to the [VCache] section of your win.ini file: MaxFileCache = 524288."' It should be system.ini. Also: did you try a static Vcache, setting MinFileCache and MaxFileCache to the same value? Best start with 1024 both, most stable setting available, but slowest. And with WinME you can't use SMARTDRIVE.EXE -limited to 128G(i)B partitions- to speed-up things (unless you make WinME real-mode aware).
  15. This means 128 entries in each cluster (each entry is 32 bytes). So your cluster-chain is already quite long in C:\DOS, deleted entries and Long File Names not counted about 7 clusters. I watched the 'behavior' of the Windows 10 FAT-driver. It seems first free entries are used, so historical order is maintained. If last cluster in the cluster-chain has no free entries anymore, the driver will recycle deleted entries first. Historical order is broken. At some point (not sure if whole cluster-chain is searched for deleted entries) a new cluster is added to the cluster-chain. Historical order again. Be aware I am talking about impressions in case of Windows 10 FAT-driver, not solid 'facts'! So do not worry about your directory C:\DOS\GAMES is not last, it should be first! The longer the cluster-chain, the longer the search-times. And: the FAT lookup-table is searched only if the first directory-cluster is full and a second is added (reading files is same: if filesize exceeds clustersize). I remember my most responsive Window-system EVER was Win95 OSR1A on Asrock A59-pro, with slightly overclocked PCI-bus. That time I owed a 20GB IDE-disk, on FAT16 I could only make 2GB partitons, but with 32KB clusters! So instead of main directories like 'My Documents' I used a new 2GB partition instead, with volume-name 'Documenten' (Dutch).
  16. How many entries are in your directory C:\DOS, and what is clustersize in the C-partition? You can read-out clustersize with CHKDSK. Judging from your post of 'Saturday 6:28 AM' you are using FAT32.
  17. About your experiment: I am not satisfied. You better make a fresh, new directory and ONLY use MKDIR on it, or copy files to that directory. I do not know how the FAT-driver behaves with your method of creating files. The FAT-driver can look for the first empty directory-entry (starting with 00h) to write a new entry, or re-use a deleted entry (starting with E5h). Both not included in @RainyShadow's picture. I doubt if 'vanilla'-DIR will 'make' any 'decisions'...
  18. There IS an order, order of read-out of directory-entries. Before any file-deletion: historical order. You can use SET DIRCMD=/W, in a session, ready after boot if set in AUTOEXEC.BAT. Remove in a session with SET DIRCMD= and so on.
  19. Sorry, lowest Q-number on my computer is Q192425 (I am more 'in' Win98SE ). However I 'found' a higher version of VPOWERD.VXD, maybe you can use it. vpowerd 4.00.1111.zip
  20. @iMic I found something on my computer. According to the INF-files inside this is UPD961018a and will update HSFLOP.PDR, INT13.VXD, IOS.VXD and VFBACKUP.VXD. Archive contains DISKTSD.VXD too. All files are ProductVersion 4.00.1111. All files except DISKTSD.VXD are FileVersion 4.00.1112 (DISKTSD.VXD is FileVersion 4.00.953). BTW: Modification Time of 1112-file versions seems to be adjusted one hour by (stupid!) Windows', because of Modification Date. But Command Prompt seems to give the 'right' time. I hope this the version you are looking for. FLOPUPD.EXE
  21. Sorry, typo indeed, corrected in earlier post. 3GB should be MaxPhysPage=C0000
  22. No correction needed, you are right. I said earlier: each 10000 MaxPhysPage stands for 256MB Window's memory. I prefer memorizable and usable units And 3 x 4 x 10000 is C0000 in hex. One Page = 4KB https://wiki.preterhuman.net/Specifying_Amount_of_RAM_Available_to_Windows_Using_MaxPhysPage BTW 10000h x 4 =
  23. It's strange, but if it is working on your system... But 3GB is still C0000, so better use this value for MaxPhysPage. Maybe you can found *something* in the documentation of RLOEW's memory patch.
  24. If your system is okay with HDATSR.EXE and *some* MaxPhysPage setting, better use these settings together. I vaguely remember RLOEW said *somewhere* that occasionally a high setting of MaxPhysPage is needed with his memory patch. Of course you can stop experimenting at MaxPhysPage=80000, but it would of interest to the community to go as high as possible, so around max C0000 SystemReg=0 disables SCANREG.EXE during Windows' boot. See https://www.mdgx.com/msdos.htm

  • Create New...