deomsh

My floppy drive is still in good shape. I did many, many tests with my stopwatch. Reading from a floppy is still too fast to give real differences, but writing does. With switch '/V' copying takes about 1.5 times longer than without. And: copying gives at least one floppy-access 'sound' extra. With 'SET COPYCMD=/V' speed is same as without switch '/V'. My conclusion is that switch '/V' is NOT supported in COPYCMD in MS-DOS 7.1. Maybe just an urban myth I have been following for many years. Sadly i can't find any source. But I found another option: 'VERIFY ON|OFF'. Timing same as with switch '/V'. If used in AUTOEXEC.BAT should working globally (also in all MS-DOS Windows). I asked Copilot if 'SET COPYCMD=/V' is valid, which is doubted by this machine. Interesting source: this conversation. See https://copilot.microsoft.com/shares/1dzXRdWHaiHyJrBShe6uh BTW Copilot mentioned too COPYCMD is not 'natively supported' in MS-DOS - so this machine does not seem to have access to the 'Technical Reference MS-DOS 6.2'.

Good idea, I will look if my old floppy drive is still working. To be continued...

Using a debugger is a bit above my level, but thanks for your suggestions. I did some tests with a stopwatch to see if there is a big difference in copyspeed, simply using COPY without '/V' and with '/V' on the command-line, but no conclusive results so far. To be (more) sure about the placement of /V and /Y in SET COPYCMD I tried your (Gemini's) earlier suggestions too in Virtual Box, and it seems '/Y' must always come first. See following print-screens (Dutch MS-DOS 7.1): I looked in some of my MS-DOS' books, for instance 'Technical Reference MS-DOS 6.2' mentions only 'SET COPYCMD=/Y' (or /-Y).

Thanks a lot. Testing is a bit difficult. I thought I could try with reversed order, for instance: SET COPYCMD=/V,Y but this is not taken, /Y must come first, like in the COPY-syntaxis. No idea how I can test the V-part. I use it just for safety, because I have to copy files on a USB Flash drive in legacy mode.

I have a basic question about MS-DOS batchfile: syntaxis of COPYCMD. Should I use: SET COPYCMD=/Y,V or SET COPYCMD=/Y,/V or is there no difference and can I use both? BTW internet search gives no results in this case (for me).

Add MinFileCache=1024 and on next line MaxFileCache=1024 and reboot. There is a good chance this will cure copy-errors.

What are your values in SYTEM.INI, [vcache] ?

Thanks, good to hear lower wait1 and wait2 are working on your system. About stability: same erratic behavior with vcache at 1024? Higher MinTimeSlice set in SYSTEM.INI can improve stability, but your system will become less responsive. Default is 20 (ms) without any setting in [386Enh]. If you want to try, just add: MinTimeSlice=40 and reboot. You can go up in steps of 20. Highest value I ever needed was '120'. About midi: you can try the Yamaha synthesizer. It's all in this thead. Just search for 'midi'.

Congratulations. I'd like to know for my notes regarding the High Definition Controller of your Intel 81 chipset: was pcipatchB=$7900 really needed, or does pcipatchB=$0000 the same?

See: https://msfn.org/board/topic/186747-can-anyone-help-me-to-install-high-definition-audio-device-on-realtek-alc887-chip-especially-deomsh/#findComment-1278735

There is no specific HDAICOUT.HDA for ALC887 as far as I know. Using another tailormade one depends first on the same Codec Index mentioned in HDACFG.INI. I have an ALC887 codec on my Asus board P8H61E. All I needed is two settings in HDACFG.INI: 1) pcipatchB=$7900 (Option on Intel H81 chipset too) 2) VolumeWidget=$0C As always: writing to chipset controller registers with pcipatchB is at your own risk (if any).

Thanks for testing. As such we are done. Actually there are a few loose ends I'd like to now about your system. First is regarding wait-states in HDACFG.INI. Defaults are: wait1=$100 wait2=$100 I you have some spare time please test both wait1 and wait2 with following values: $80, $60, $40, $20 - until you are experiencing some sort of problems. If $20 is still good, then go on with $15, $10 and $5. Even lower better in steps of '1'. Always reboot Windows in between. Also there is a (possible) reward: the lower the shorter you have to 'wait' during starting Windows (in my experience).

Good to hear. I made a normal version of HDAICOUT.HDA for VT1708B with minimum number of verbs. I removed the GET-verbs and commented out Node ID 25, can be activated again at any time (and by switching the Selector Widget in Node ID 1D, or by enabling Input 5 in Node ID 16). Node ID 1C is still active, so a Speaker connected to that node can be driven. DAC0 at Node ID 10 is set to to Stream 1/ Channel 0 and 44.1kHz/ 16-bits. The commented-out verb just below is for switching to 48kHz/ 16-bits. Headphone-amplifier is enabled for Node ID 1D, if this gives noise, switch to normal output (Commented-out verb just below). I added Power Up verbs to all remaining nodes, just in case a laptop-user with codec VT1708B wants to try. I hope this (hopefully) final version is still working. HDAICOUT_VT1708B.HDA.000

Great! With 'volume adjust as well', did you mean WAVEOUT.EXE?

Thanks. I checked everything. Please try debug-version. IF this version gives sound in your Windows 98SE installation, you can try in HDACFG,INI: SleepingWidget=$10 VolumeWidget=$1D OutputWidget=$10 If VolumeWidget is right, WAVEOUT.EXE should be working too. I'd would like to see HDAICIN.TXT of VERY cold Windows 98 boot afterwards. HDAICOUT_DEBUG4_VT1708B.HDA