deomsh

There no Windows 98 driver. HDA2.DLL, the driver mentioned in this thread is a Windows 3x driver. Use in Windows 98 is experimental. HDAICOUT.HDA is a file used by HDA2.DLL to give certain presets to the High Definition Audio Codec.

This is really great! Works perfectly with a 2880KB floppy image in Virtual Box 6.018. Thanks a lot! Only drawback: editing a g4b-file is more addictive now than using EDIT.COM on a (slow) USB-pendrive. A few month ago I tested Grub4dos with VBox, chainloader /io.sys didn't work. This time no problems, whatsoever.

It was more ment as a warning. The creator of copyFF.bat is absolutely a genius. I did some more tests, using my old MSYS USB1.1 16MB pendrive. It appears that fat mkfs and fat mkfile are not fully-fully safe. But 'a picture paints a thousand words', so here they are: http://imgur.com/a/5cZHjdG

I was mistaken, copyFF.bat is parsed too. But it's VERY dangerous, I run the file accidently without arguments and found the FAT of my (USB-)rootdrive rewritten, probably by the fat mkfs line in copyFF.bat Luckily I made a full backup just before testing copyFF.g4b. Better add some sort of validation.

Thanks for the links, command --set-ext=.g4b in MENU.LST just before commandline saves time during testing (in my case the "4" easily becomes a "r"). In the post from 18 October 2013 - 01:27 PM you asked for an EDIT tool in Grub4Dos. Exists such a tool? Would be great, testing / correcting a longer Grub4Dos batch-file is very time consuming without.

Yes, I have red the comments. Sadly enough I didn't solve the issues. Reason: there are no issues (except not copying LFN), at least not with grub4dos-0.4.6a-2019-09-09. Only thing I changed: renaming copyFF.bat to copyFF.g4b to make batch file working. I used following commands: (fd1) because of my real floppy drive (fd0); and only enough space on (hd0,5) for the iso: From Grub4Dos Command-line: grub> --------------------------------- map (hd0,5)/WXPhome.ISO (0xff) map --hook copyff.g4b (fd1) 0x1A0000 /I386 map --floppies=2 root (fd1) --------------------------------- To be sure: this is the content of my copyFF.g4b ---------------------------------------------------------------------------------------- copyFF.g4b ---------------------------------------------------------------------------------------- !BAT # Usage call (bd)/copyff.bat (fd0) 0x1A0000 /I386 # 1st param - e.g. (fd0) or (fd1) = virtual drive to create in memory must be fd0 or fd1 # 2nd param - e.g. 0x1A0000 - size of virtual drive # 3rd param (optiona) - e.g. /I386 - subfolder to start copy from debug off errorcheck off # initialise filecounter # write 0x60000 0 # stop 'hit Q to continue' messages pager off #512MB = 0x100000 #850MB = 0x1A0000 #1GB = 0x200000 set FD=%1 map --mem (md)0x300+%2 %FD% map --hook insmod (bd)/fat debug on clear echo Copy (0xff) contents to virtual drive %1 (size=%2), starting at %3... fat mkfs %FD% if NOT "%3"=="" fat mkdir %FD%%%3 debug -1 pause --wait=3 debug off root (0xff) set cd=%3 call :cpa echo Finished! goto :eof :cpa clear echo Copying files in folder: %cd% ::Change source root root (0xff)%cd%/ ls | call :copyfiles echo Finished folder %cd% goto :eof :copyfiles if "%1"=="" goto :eof ::If is a directory cat --length=0 /%1 || goto :sub-dir ::copy file echo %cd%/%1 fat copy /%1 %FD%%%cd%/ > nul || echo Error: %cd%/%1 # Filecount printed # debug on # calc *0x60000++ # debug off shift goto :copyfiles :sub-dir setlocal fat mkdir %FD%%%cd%/%1 set cd=%cd%/%1 call :cpa endlocal shift goto :copyfiles ---------------------------------------------------------------------------------------- Here are the results (pictures taken by daylight AND my first IMGUR experience EVER). Still only 20KB left on my msfn account......... https://imgur.com/gallery/g8Awwwf Enjoy!

I discovered problems while copying from a Grub4Dos command-line to rd2hdf16.g4b/rd2hdf32.g4b based memdrives , map --rd-base is still not high enough. I am working on a copy-tool using Grubutil fat to copy to FAT-devices. My copy-part is based on COPYFF.BAT I found on https://www.rmprepusb.com/tutorials/grubutils - I hope that's not a problem. First I tested on USB drives only, which gave no real problems. Lately i started testing copying to Grub4Dos (rd) to (hd) mapped devices. It appeared that even 42MB wasn't 'good'. Copying stopped at about 400 files and fat dir gave out of memory errors afterwards. On https://www.rmprepusb.com/tutorials/grub4dos/grub4dos-internal-variables-and-functions I found, (md)-related, using above 50MB the Grub4Dos memory area 'to be ultra safe!'. Also wenv/insmod is mentioned loading files above the 32MB memory area. With map --rd-base set to 50MB all copy problems while using Grub4Dos, where gone. Even copying a directory containing 5,000 files. Updates of both files: in the posts of February, 27 and March, 11

Thanks for the report. Interesting, especcially in case of rom-dos 7.1. It's sad that there is no free evaluation version, in the past there should have been one. I will take look in my archives. About size-differences: MS-Smartdrive can become really big too, depending on cache-size and size of Read-Ahead Buffer. See for documentation the start of this thread. I have tested R. Loew's second patch on 240GB logical partitions, on two different 500GB Sata Hard disk's, with mixed results. Write-behind caching was always a no-go, as expected. With SMARTDRV /X I had on one disk same results you already mentioned. But to the other disk I could copy 60GB in MS-DOS without problems (the partition had about 125GB files before I started copying). Only with minimum Read-Ahead buffer of 16KB (to me /B:32768 or higher makes more sense because of the 32KB cluster-size - but not sure about that). A side-note about SCANDISK.EXE (not SCANDSKW.EXE in Windows!). Can run out of memory, if errors are found on big partitions. I cured this by using SCANDISK /custom and set SCANDISK.INI to make no log file. Also it's good to set "delete lost clusters", because of available filenames for CHK-files.

Thanks for testing Which version of SMARTDRV.EXE did you use?

I asked for a link and a legal way to get access to this file. I spend in between two ours reading about Vista beta versions, but I found no way to get this file. I have never been a beta tester, and all (pre-)Vista betas will be not accessible to me. But I have Windows XP/7/10, is there a 'similar' version I can test?

Good question, in the TBPLUS-package there are two SMARTDRV.EXE versions, (30-04-10 and 11-06-18). They are both different from the MS-2000 version. I will test soon!

'Officially' partitions > 128GiB are not supported by Smartdrive. Did you try the /X switch? This is the Read-caching mode, so no Write-caching. It would be of interest to try loading SMARTDRV /X /B:57344 and than giving DIR /S

A fresh installation is always good for testing purposes, and I believe: best vanilla as possible. Did you use any unofficial service packs?

Nice, you're lucky with such a board. But doesn't seem SATA to me, in Windows drives will NOT run in MS-DOS Compatibility Mode. I took a look to the 815T chipset, P-III isn't it? I found boards that has ICH2-Southbridge with a 100MB burst mode. I doubt BIOS-hacks are possible (and as far as I know MSFN wouldn't like that on their forum). In this thread I used copy speeds in MS-DOS as a sort of benchmark to compare with Windows' MS-DOS Compatibility Mode. I am not aware of good speed-testers in MS-DOS. In all my tests I copied the same 496MB file between two hard disks and recorded the time with my sons stopwatch.

I am more than happy to attempt this despite the great danger you mentioned So, I am modifying the Kstub822 file to include these stubs Although I can not test on WinME, messing around with stubs shouldn't be needed in case of MPC-HC 1.7.5 and with SHLWAPI.DLL from IE5.5 or higher. The unresolved dependencies I showed you are harmless in my case. Please delete stubs in core.ini and try again. The right registration of Jumper's UXTHEME.DLL is more important, together with the right way to substitute MSVCRT.DLL

I was trying to help a member with problems regarding MPC-HC 1.7.5, which took several ours to revitalize old installations. I can't test in between other MSVCRT.DLL substitutes or discuss them from schratch. If you ask for help I am willing to test, but I need LEGAL access to the file-version mentioned. BTW I don't possess Vista.

I tested MPC-HC 1.7.5 with Kex18, not with higher versions. Further: I have used Win98se ONLY !! Version max: MPC-HC 1.7.5 (537b5a3) - Kex for MPC-HC.EXE: XP-SP2 (installer needs 2003 SP1). Stubs shouldn't be needed, unless you use (like I did) Vanilla Win98 without IE5.5 - in that case for some functions ONE stub for SHLWAPI.DLL is needed. About: MSVCR70/MSVCRT: registering is the wrong way. Best go to the registry: HKLM\System\CurrentControlSet\Class\SessionManager\KnownDLLs\ and set (String !) MSVCRT to MSVCR70.DLL and reboot. Dont rename MSVCRT, but change value to MSVCR70.DLL. I have no opinion using MSVCR80.DLL as a MSVCRT-substitute. About UXTHEME: copy Jumpers' UXTHEME.DLL to %winbootdir%\Kernelex\Kex\ (create folder 'Kex' if needed). Go to registry-key: HKLM\Software\KernelEx\KnownDLLs\ and set (String !) UXTHEME to KEX\ UXTHEME.DLL (original PSAPI.DLL should already be in this key (and in the KernelEx-folder): PSAPI= PSAPI.DLL. About starting the media-file: Sometimes press Stop first - after opening a file, then Press Start again. This is shown by ImportPatcher on my system (same options as on your picture; ImportPatcher 4.1 set to VISTA - If I remember well that's according to Jumpers instructions): ---------------------------------------------------- [Patches needed] [ntdll.dll] NtStopProfile= NtCreateProfile= NtSetIntervalProfile= NtStartProfile= NtWriteFile= NtSetInformationProcess= NtQueryInformationProcess= NtQueryVirtualMemory= NtQuerySystemInformation= [KERNEL32.dll] HeapQueryInformation= [USER32.dll] SetLayeredWindowAttributes= ----------------------------------------------------- Be aware MPC-HC 1.7.5 is somehow dangerous, crashes can be severe. Destroyed more than once my entire installation. I never reported this app in this thread!

My link is working on Android/Chrome Your link gives the same file as far I can judge

You can try Craig Hart's PCI-AGP Sniffer. The DOS-version is updated up to 2002, but will take 2007' PCIDEVS.TXT from the PCI32 version on Majorgeeks. A few years ago I used this PCIDEVS.TXT to read out HD-Audio PCI-controller registers. After a short experiment it seems to me the DOS-version accepts other / newer PCIDEVS.TXT to, like the 2018 version here. https://ecsoft2.org/pciagp-bus-sniffer-ids2devs PCI-E Devices are identified too.

Do you want a DOS app to read out PCI registers?

I never tried adding MSVCR70.DLL to KernelEx known dll's. Higher versions of MPC won't work with Win9x MSVCRT.DLL, so go to (real) MS-DOS and rename MSVCRT.DLL to MSVCRT.ORG and then rename MSVCRT70.DLL to MSVCRT.DLL (in %windir%\SYSTEM). Or: copy MSVCR70.DLL to %windir%\SYSTEM and set in the Registry in key (regular !) KnownDll's MSVCRT=MSVCR70.DLL and reboot. One year ago I tested all available versions of MPC-HC with Kex 4.5.2016.18 (not the portable one's if I remember well).

Which version of KernelEx are you using? And are you using MSVCR70.DLL renamed to MSVCRT.DLL

I gave you my inf-lines because you asked 7772 users. Your inf-file is a 8269 version. This file is different from the 7772 one. I haven't used 8269 in the last years. I used 8269 for my 7900 GTX and my 7950 GT. They both died in between. I never liked 8269 because of shutdown/dosbox problems. If you are going to use 7772 (international) and have made entrances to THAT version of the inf-file I will try to judge your entrances, or try to give other help.

This is my card: http://hw-museum.cz/vga/193/medion-geforce-6700-xl I added to NVAML.INF: [Mfg] %NVIDIA&DEV_0147.DeviceDesc% = NV30, PCI\VEN_10DE&DEV_0147 [Strings] NVIDIA&DEV_0147.DeviceDesc="NVIDIA GeForce 6700 XL" In 8269/NVAGP.INF is more information about which NV to choose, but lines should be like the one's in NVAML.INF.

I am happy with my 128MB PCI-E 6700 XL and the 7772 drivers after adding the device to the inf-file. The RUN/RUNSERVICES lines better delete in the inf-file, always problems, and they are not needed. Do not touch the line with RUNSERVICESONCE !