deomsh

Motherboard Asrock N68C-S UCC is also compatible with Part 8½ B: Full installation of Windows 98se on a Rloew non-XMS Ramdrive. But this was not that easy, so maybe of general interest. This board has a Nforce 630a chipset (max 8GB). In a conversation between @ragnarok and @LoneCrusader the problem was mentioned of endless waiting before Windows 98SE started, should have to do something with 'Gate A20 line': https://msfn.org/board/topic/174701-w9x-on-geforce-7025-nforce-630a-chipset/ I fixed my waiting-problem during setup with SweetLow's HIMEM.SYS: http://sweetlow.orgfree.com/download/ and then file a20alwon.zip The 'preferred' version is fully compatible with my 'WINONR 8.5 USB' setup - only manually copying HIMEM.SYS to directory SETUP982\DOSFILES is needed. But after last part of Windows Setup: still only a blinking cursor - while I was using 'Setup /p i'. In the end following workaround gave the desired result: installation with setup-switch /p i;s=detectbus,detectfloppy. This time there was no problem to start the GUI of Windows 98SE. I used my NUSB33 setup-choice already, after Wizard New Hardware to install the PCI-bus all USB-devices were recognized - without reboot! After copying to the USB-pendrive, running Windows 98SE was no longer a problem. No waiting either. IDE- and SATA-Controllers are working too with RLOEW's patches. Only the onboard LAN (RTL8201EL) was not recognized (also no driver available). The onboard-graphics Geforce 7025 can only be used with Bearwindows' VBEMP driver, but this was a known fact already. Even Watler's HDA-driver is working with the chipset's HDA-controller (10DE:03F0). The VIA HDA-codec VT1705 is working out of the box, to use WAVEOUT.EXE only VolumeWidget=$10 has to be set in HDACFG.INI. But there was one persistant problem: exit to MS-DOS was no longer possible, and shutdown or reboot only while using the pysical buttons. I tried the Shutdown Supplement and other updates/ registry-hacks, but to no avail. In the end overwriting the NUSB33-stack with the one in U98SEUSB.EXE from @PROBLEMCHYLD Unofficial 3xx-Servicepack solved all these problems (do not forget to disable SystemTray in MSCONFIG and renaming NTMAPHLP.PDR). With addition of an old RTL8139 PCI Ethernet card everything is GOOD, even Safe mode is working. BTW: if an ACPI-bios was installed manually, almost everything seems okay (except one instance of Motherboard Resources with yellow exclamation mark), but no ACPI functions - same functionality as with PCI-bus only. But Wizard New Hardware didn't find a BIOS in auto-mode.

Part 8½ B: Full installation of Windows 98se on a Rloew non-XMS Ramdrive This project is a variation of Part 8½ A: Full installation of Windows 98se on a Grub4Dos Memdrive, but this time the Grub4dos memdrive is only used to obtain a small C-drive to install and run Windows 98se on a Rloew non-XMS Ramdrive. Tested on following systems: 1) Asrock 960GM-GS3 with 2GB, 4GB and 8GB RAM, AMD-Bulldozer and Geforce 7800 GTX v2 2) Asus P8H61E with 8GB RAM, Intel i-3 and NVIDIA GeForce 6700 XL 3) Acer VERITON M2610G with 2GB, 4GB and 8GB RAM Apart from the content of the Windows 98se CD-ROM, only eight additional files are needed: Files HIMEMEX.SYS, RAMDSK32.COM and RAMDSK64.COM are needed to create the non-XMS Ramdrive(s). PROTHOOK.VXD is needed to give Windows' access to the Ramdrive(s) - https://rloewelectronics.com/distribute/RAMDISK/RAMDISK2.0/ File LCOPY.EXE from LFNTOOLS is used to copy Long File Names to the Ramdrive, while still in MS-DOS. LDEL.EXE is used for special purposes. Inside lfn-1.79-en.zip - https://sourceforge.net/projects/lfntools/files/lfntools/1.79/ Files GRUB.EXE and grubutil FAT are needed for phases using Grub4dos - latest grub4dos-0.4.6a-2024-02-26.7z - https://github.com/chenall/grub4dos/releases/tag/0.4.6a The attached zip contains only my own MS-DOS batch-files, a couple of my own Grub4dos-scripts, a few modified INF-files, some PIF- and LNK-files and documentation. Highlights minimal user-intervention needed, two small image-files auto-added during Setup script INSTALL.BAT will check for presence of obligatory files and will extract all other needed files from the Windows 98se-CAB's includes a new script to patch RUNONCE.EXE during Setup (from Grub4dos). auto-adjustment of Ramdrive(s) to 1GB 32-bits ramdrive (2GB RAM), 2GB 32-bits ramdrive (less than 5GB RAM) and 2GB-swapfile 32-bits ramdrive and a 64-bits ramdrive (from 5GB of RAM) setup can be run again re-using all files, images re-used if desired too predefined drivers available during installation by copying files to their respective directories Bearwindows VBE graphics driver Tihiy's Safe mode SVGA-patch BHDD31 NUSB33 Rloew's PATCHMEM, HCDP, SATA patch, AHCI-driver and USB1-storage driver Sweetlow's RMMFLRM.VXD to delete phantom floppy drive letters Update Windows files placed in directory WINDIR or inside sub-direcories INF, COMMAND, SYSTEM, SYSTEM\IOSUBSYS or SYSTEM\VMM32 Bootmenu after installation, with choices Normal, Logged (\BOOTLOG.TXT), Safe mode, Command prompt only and Safe mode command prompt only (if defined MS-DOS CD-drivers are added, choice Command prompt only with CD/DVD too) Injection of changed CONFIG.SYS and AUTOEXEC.BAT and driver-files on small C-memdrive possible (directory INJECT.ONC) Everything is documented in the directory README in the Project-zip below Some print-screens made during installation: Content of README.TXT REQUIREMENTS: 1) USB-flashdrive formatted with FAT or FAT32 (depending on size) including MS-DOS 7.1 system files 2) HDD-style is most universal, but FDD-style is possible (probably no Safe mode) 3) Content of Windows 98SE CD-ROM 4) Prod-key to install Windows 98SE 5) Minimum of eight additional files: HIMEMEX.SYS, RAMDSK32.COM, RAMDSK64.COM, PROTHOOK.VXD, LCOPY.EXE, LDEL.EXE, GRUB.EXE and FAT HARDWARE: 1) Minimum 2GB memory, preferred 8GB 2) Best is a PS/2-Keyboard, otherwise NUSB33-files must be included in Setup, needs USB1(.1) 3) Mouse is not needed during Setup PREPARATION: 1) Copy contents of WINONR8.5.USB.EMPTY.ZIP to USB-flashdrive 2) Copy files of Windows 98SE CD-ROM to directory WIN982CD 3) Copy minimum of needed files to directory SETUP982\ADDFILES (see ADDFILES.TXT for specifications) 4) Copy desired files to various directories to run during Setup (see files-lists with specifications) 5) Copy desired drivers to directory SETUP982\DRIVERS (the content of this directory is copied to R:\SETUP982\DRIVERS, including sub-directories) 6) Copy desired programs to directory SETUP982\PROGRAMS (the content of this directory is copied to R:\SETUP982\PROGRAMS, including sub-directories) INSTALLATION: Boot from USB-flashdrive and run INSTALL.BAT AFTER INSTALLATION: 1) Use MSCONFIG to disable SCANREG and Schedules - do not reboot! 2) Disable Recycle Bin 3) Enable DMA in Device Manager on Hard drives/ CD-ROM - do not reboot! 4) Installation of USB-drivers if still needed - do not reboot! 5) Installation of other drivers of choice - do not reboot! 6) Boot to MS-DOS and Exit to Windows (automated with pre-installed Shortcut on Desktop) 7) Copy content of R: to directory ONR on USB-flashdrive (best with function Directory Synchronization of Total Commander) RUNNING WINDOWS 98SE ON RLOEW'S NON-XMS RAMDRIVE: Boot USB-flashdrive and use Menu-item of choice After choosing item Command-prompt only, Windows can be still started with WIN, even in Safe mode with WIN /D:M After choosing item Safe mode command-prompt only, Windows can be still started with WIN, but NOT in Safe mode MAINTENANCE: 1) Safe mode can be used for maintenance, rather slow (not working on all hardware - needs USB1.1) 2) Windows can be used for maintenance, needed for certain drivers. Before reboot synchronize R: with directory ONR on USB-flashdrive Afterwards again to delete installation files in directory ONR\WINDOWS.ONR From command-promt there is access to the Windows-directory WINDOWS.ONR (is using SUBST.EXE R: C:\ONR) TROUBLESHOOTING: 1) USB2-drivers: if drivers from NUSB33 are not working, use U98SEUSB.EXE from Unofficial Service pack 3xx After installation reboot Boot to MS-DOS and Exit to Windows (automated with pre-installed Shortcut on Desktop) Finish installation with Device Manager 2) NDIS-2 driver needs an entry in AUTOEXEC.BAT, install from Windows Before reboot check AUTOEXEC.BAT on small C-drive and move entry AFTER file-coping entries Copy modified AUTOEXEC.BAT to directory INJECT.ONC on on USB-flashdrive 3) DirectX can be installed in Safe mode, but after reboot to Windows installation files must be removed from directory ONR\WINDOWS.ONR on USB-flashdrive 4) HDA2 driver needs an entry in AUTOEXEC.BAT, add HDATSR.EXE manualy from Windows to AUTOEXEC.BAT and HDA2.DLL to SYSTEM.INI Use AUTOEXEC.BAT on small C-drive and set entry AFTER file-coping entries Copy modified AUTOEXEC.BAT to directory INJECT.ONC on on USB-flashdrive 5) Localization of MS-DOS can be added to CONFIG.SYS and AUTOEXEC.BAT on small C-drive Copy modified CONFIG.SYS and AUTOEXEC.BAT to directory INJECT.ONC on on USB-flashdrive 6) Copying small C-drive back to image-file 16WINONC.IMG with help of hex-tools like HxD Copy content of Physical drive back to image-file (NOT logical drive) BTW file 16WINONC.IMG is set to System and Read-only, so temporarily remove Read-only attribute 7) Instabilities while using non-XMS Ramdrive: Adjust Buffers in CONFIG.SYS on small C-drive and copy to INJECT.ONC Disable Read-ahead buffers on HDD and CD-ROM in Device Manager

As far as I know, HDATSR.EXE creates a buffer in memory. Without use by HDA2.DLL, the buffer will remain empty.

@ctral Better stop testing, Rloew once mentioned the PCIe-bus can become overheated:

@ctral sorry to hear HDATSR.EXE is overheating your system. I suppose you did not use LOADHIGH. Good luck with your USB-Audio!

@Wunderbar98 nice to see you around

Sorry to hear that. Your system seems to be a bad fit with HDA2.DLL. I have no new ideas.

I use DirectX 9.0c all the time, but I am not sure about the difference without (so version that comes with Windows 98SE CD-rom, I believe version 6.0 or 6.1 ??). Lately I tried HDA2.DLL before installing DirectX 9.0c, but I quickly installed it because I needed the mp3-codec inside.

That's already high. The highest value I ever used is MinTimeSlice=120 Currently I am working at a project to run Windows 98SE on a 64-bits ram-drive. I get only stable results with double buffering. Maybe you can try with the line DoubleBuffer=2 in MSDOS.SYS under [options]

This error is thrown by HDA2.DLL. What value of MinTimeSlice was in use in SYSTEM.INI?

Did you try VBEMP to rule-out graphics card driver problems? HDA2.DLL is a driver made by 'Watler' for Win3x !!!! Use on Windows 9x is FULLY experimental. But your system MUST be stable before trying HDA2.DLL. Updating Windows 98SE makes no sense, start with a basic SETUP /p i installation and VBEMP as graphics driver. Further 98KRNLUP.EXE KRNLUP98, BHDD31.ZIP, RLOEW's two disk patches (for IDE and SATA) and his memory patch, if needed with the /M switch. BTW: link to HDA2.DLL's in HDADRV9L.zip and HDADRV9J.zip on my Google-Drive: https://drive.google.com/drive/folders/1kvmrcmZbnkNm8Y2z3uyPHNKjxNR70MVM?usp=drive_link Be aware HDAICOUT.HDA in the zip's are Watler's examples, not my version(s)! HDADRV9L.zip is same as the current version on Watlers site: http://turkeys4me.byethost4.com/programs/?i=1

I you don't specify a CONFIG.SYS, Windows will load some default settings. [vcache] settings you mentioned in SYSTEM.INI should give more stable results. Adding MinTimeSlice=80 under [386Enh] can help too, or another value above 20 and max 120. SMARTDRV /X /L /V /B:57344 will speed up your system (in AUTOEXEC.BAT). I can't help you with your graphics card. Try VBEMP to rule out graphics driver problems.

Don't know if you have to re-install. Is everything 'normal' if you comment out the HDA2.DLL line in SYSTEM.INI? BTW you don't have CONFIG.SYS?

How is sound and stability (Explorer error you mentioned)?

According to HDACFG.INI your 'CODEC Index=$1', but this is the internal soft-modem.Can you switch it off? The HDA-codec is at 'CODEC Index=$0' according to HDAICOUT.TXT. This will be Realtek HDA-codec ALC883. During troubleshooting add following line in SYSTEM.INI to [386Enh] (.....) MinTimeSlice=80 Please report, and upload again if anything changes in HDACFG.INI

UPLOAD again: HDACFG.INI

Your AUTOEXEC.BAT and SYSTEM.INI looks good, although SMARTDRV /X is more safe. But HDACFG.INI is not populated, only Busmaster values. This file is written by HDA2.DLL, always in your Windows directory. Only HDA2.DLL is in the System directory! Please delete ALL instances of HDACFG.INI, reboot and upload this file again. Do NOT edit anything for now.

Please upload following files, so I can take a look: CONFIG.SYS AUTOEXEC.BAT SYSTEM.INI HDACFG.INI

Are you using Windows 98SE or Windows ME?

Lately I finished a second version of MKFATIMG.G4B, a Grub4dos script to make FAT-image files: https://github.com/deomsh/MKFATIMG.G4B This script descends from an earlier project in this thread: to write a FAT-volume on a ram-disk and map to hard-disk. See: https://msfn.org/board/topic/180597-exploring-setup-p-isdetectbus-and-grub4dos-8½-times-win98se-on-usb-drive/page/4/#findComment-1178197 However, the new script is more universal, only mapping is not a part of it anymore. But the chosen FAT-volume is still written (partly) to a ram-disk first, before dd-copied to file. File-creation uses Grubutil 'FAT'. In latest version 0.4 of MKFATIMG.G4B Loosely Linked Libraries mentioned in previous post can be applied to use Long File Names (FATLFN.LLL with dependency ATTRIBFT.LLL). If these libraries are not found, only Short File Names can (still) be used. The Small-help shows four modes of use: Instead of targeting an image-file, also writing a FAT-volume on a ram-disk '(rd)' is possible, only limited by available (high-)memory. But if an image-file is targeted, max 64MB is written to the ram-disk and later dd-copied to the start of the image-file. Because production of the image file with grubutil 'FAT' is only possible on a FAT-filesystem, maximum image-size is < 4G(i)B. If only 'size' and target are specified, there will be a disk-type and FAT-type produced depending on that size only, with no bootcode and no label, but with a valid MS-DOS uuid so each image is unique (unless some Swiss watchmaker is involved). Up to 4MB a floppy-image with FAT12, above up to 16MB a harddisk-image with FAT12, then a FAT16 harddisk-image up to 512 MB and above a FAT32 harddisk-image. Instead of 'size', also number of 'sectors' (512-byte only) can be specified, or even 'C/H/S'-values. With what I call 'Use 1', there are numerous switches to specify desired properties of disk and FAT-image. With 'Use 2' and 'Use 3' there is access to a set of predefined floppy-images or (old) AT/PS2 disk-types for harddisk-images. Still many switches available. Values used for predefined floppies are most of the time grabbed from 'Known_floppies2.xls' of Jaclaz: As an example a print-screen of the making of a 12240KB floppy-image while using Long File Names. According to my tests this is the biggest floppy that can be used with VMware: BTW if the switch '/BOOT' without ':OS' is used, the standard Win9x-bootcode will be written to the PBR, different for FAT12/16 and FAT32 (and to the MBR too in case of a harddisk-image). Script MKFATIMG.G4B has numerous bootcodes in textual form 'on board'. From MS-DOS 3.3 upwards, Freedos, ReactOS and Grub (Grub-bootcode is written to the PBR only). More information is in the Help. As a specimen I produced two 12240KB floppy-images (one without bootcode). Also two 3840KB floppy-images (one with Grub-bootcode too, and one without bootcode), because this is the biggest floppy accepted by Virtual Box (only if used from the start, no so good if changed during a session!). Use of the attached images with Grub-bootcode is simple: copy 'grldr' (comes with Grub4dos) and some menu.lst and other desired files to the image, for use in a virtual machine. Use of the attached images without bootcode: load the image with System Files of choice and boot directly using grldr grub4dos (NOT possible on MS-DOS 6.22 and below), or transfer desired bootcode too with some program like SYS.COM. As last print-screens the making of an almost 2GB FAT16 harddisk-image (values are rounded down by the script, also always ONE empty cylinder is added) together with mapping, copying Windows 98 system files and booting: BTW 'Use 4' is not showed, is used to copy an image on a ram-disk afterwards to file. With these use some files can by copied to the ram-disk first, to pre-load the image. Flop_12240k_(255t,2h,48s)_BCGRUB.zip Flop_12240k_(255t,2h,48s)_NOBOOT.zip Flop_3840k_(80t,2h,48s)_BCGRUB.zip Flop_3840k_(80t,2h,48s)_NOBOOT.zip

One of the better 'assets' if using Grub4dos is Grubutil 'fat'. Many of my scripts use this program to do basic operations on FAT file-systems. However, grubutil 'fat' can write Short File Names only. Almost three years ago I finished my first version of Loosely Linked Library ATTRIBFT.LLL, one of my ideas was to use this library to write a grub4dos script with same command-line as grubutil 'fat', but fully compatible with Long File Names. So again a front-end. This script is finished: FATLFN.G4B, and available on Github: https://github.com/deomsh/FATLFN I added a few extra switches and functions. 1) Because grubutil 'fat' does not copy the original date and time (Modification Date & Time), I added this functionality; 2) Because grubutil 'fat' can not overwrite read-only files, I expanded switch '/o' to '/o[:r]', same for deleting files ('del') with extra switch '/r'; 3) I added switch '/a', used to copy all attributes too (FAT-source only - also available in FATCOPY.G4B); 4) Function 'dir' shows Long File Names (if available). Like grubutil 'fat' always the whole directory is parsed (filtering on specific file-names would break the compatibility I wanted to be established); 5) New function 'dirx' shows Short File Names, filesize and associated Long File Names (if any). This function is more like 'dirx' in Windows 10 cmd. Also simple filtering on specific file-names is possible (ls-style); 6) New function 'dira' shows Short File Names, Attributes, Date & Time, Creation Date & Time (WRI) and Last Access Date (ACC). Filesize is not showed, not enough space in textmode/ 640x480 graphicsmode. Also simple filtering on specific file-names is possible (ls-style); 7) New function 'dellfn' will delete Long File Name only (actually not dependent on the existence of an associated Short File Name, orphaned duplicates in the targeted directory will be deleted too). Functions 'ren' and 'copy' of grubutil 'fat' are enriched with possibilties to add or change Long File Names. For example change case of a Short File Name, which for instance is NOT possible in Windows 10 (on FAT file-systems). Microsoft advises to do a two-step rename: https://answers.microsoft.com/en-us/windows/forum/all/how-to-change-file-names-from-lower-case-to-upper/2305aad9-5743-4e95-83bd-64b191e312eb This time I used the NT-method to abbreviate Long File Names: first four identical (resulting) Short File Names ('seen' as full 8+3 SFN) in a directory are tilded '~1'-'~4' after the first six characters of the name-part of the Short File Name. If more Short File Names would be identical, they have same first TWO characters, followed by a hash of the Long File Name and tilded '~1' up to '~9'. FATLFN.G4B is using following functions of ATTRIBFT.LLL: getsfnpath, getsfn, getlfn, makelfn, dellfn, isreadonly, getattrib, setattrib, getntcasebyte, setntcasebyte, getdate, setdate, gettime, settime, getdatetimeattriball and calclfnhash. I also made a Loosely Linked Library version: FATLFN.LLL (not used yet). This gives a library with a dependency to another library, because ATTRIBFT.LLL is still used. I hope I am not creating my own lll-hell . One print-screen with new functions 'dirx' and 'dira' (more on Github): BTW: it is funny the 8+3 'LOWCASEx' Short File Names have no associated Long File Name. This is because made on a NT-file-system, only - what I call - the NT-casebyte is set in the Directory-entry. No Long File Name is written if name-part, extension or both are FULLY lowcase (if only one is lowcase, the other must be HIGHCASE, otherwise a Long file Name will be written). But with grub4dos' internal function 'ls' this byte is read-out and corresponding case is showed.

A long time ago already I announced an outline of front-ends for grubutil 'fat' (and two for internal grub4dos function 'ls' too). I fully forgot my announcement, although I use all these scripts for years. Lately I finished them all and published them on my Github page. In the first version(s), all scripts could handle Short File Names only (except for ls-directory parsing in FATLSDIR.G4B). Now the other three scripts can handle Long File Names too, if the Loosely Linked Library ATTRIBFT.LLL is present. The concept of Loosely Linked Library is an idea of Wonko the Sane (Jaclaz) and discussed on reboot.pro (sadly still 'down', maybe forever?). Script FATCOPY.G4B, front-end for grubutil 'fat' function 'copy', was published earlier in this thread, latest version 0.3: Version 0.4 has following changes: Version 0.4 NEW: switch /lfn[:]@ to add Long Files Names from previously saved to XXXXXX#n/@n[.EXT]-files to 'tilded (XXXXXX~n[.EXT])' Short File Names (needed: Loosely Linked Library ATTRIBFT.LLL) NEW: switch /lfn[:case] to copy Long File Names (needed: Loosely Linked Library ATTRIBFT.LLL) NEW: switch /z to copy zerobyte-files (NOT possible if source is NTFS) NEW: switch /a to copy all atrributes on source files to target files NEW: switch /maxfiles:n to limit maximum of copied bytes NEW: switch /maxfiles:N to limit maximum of copied files NEW: dialog to overwrite read-only files, do in advance with switch /r IMPROVED: switch /sfn:@ has auto-set tilded file number by read-out of already saved Long File Names IMPROVED: protection against errors on command-line Changes to switch in use to change MDBASE Various bugfixes Script FATLSDIR.G4B, front-end for grubutil 'fat' function 'dir' or for internal grub4dos function 'ls', was discussed earlier in this thread. Version 0.1 is ready, with more than twenty switches, including basic one's like '/b', '/s', '/w' and '/p'. Like 'DIR' wildcards are supported, but only simple asterisk-wildcards (even ONE '*' at the end of last directory in PATH), switches like '/[-]x:~' and '/[-]y:DIR' can be used to filter on chars in file/ folder names. Also the special switches '/size:n' is worth mentioning, to filter on filesize. On next print-screen the use of this switch to find all zero-byte files in a directory, and in all it's sub-directories. Watch the difference between output of FAT-directory parsing and ls-directory parsing: Script FATMKDIR.G4B, front-end for grubutil 'fat' function 'mkdir', is small, compared to the other three. Purpose is to make full path, convert Long File Names to Short File Names, or write the LFN's as external attribute to file, or to make Long File Names using ATTRIBFT.LLL. Script FATLDEL.G4B, front-end for grubutil 'fat' function 'del', to to delete files and folders, or whole sub-directories, Deleting Long File Names is possible if using ATTRIBFT.LLL. As an illustration a print-screen, also with use of switch '/t', for ' trial' (Also present in FATCOPY.G4B and FATMKDIR.G4B).: All scripts, with more information an many print-screens, can be found on : https://github.com/deomsh

I found this, maybe helpfull? ; Filename: ssigd.inf [...] [......] [Manufacturer] %Intel%=Intel.Mfg ;=============================================================================== [Intel.Mfg] %Intel% %i810% = ssigd_wht, PCI\VEN_8086&DEV_7121 %Intel% %i810DC% = ssigd_wht, PCI\VEN_8086&DEV_7123 %Intel% %i810E% = ssigd_wht, PCI\VEN_8086&DEV_7125 %Intel% %i815% = ssigd_wht, PCI\VEN_8086&DEV_1132 %Intel% %i830m% = ssigd_alm, PCI\VEN_8086&DEV_3577 %Intel% %i835% = ssigd_alm, PCI\VEN_8086&DEV_357B %Intel% %i845% = ssigd_alm, PCI\VEN_8086&DEV_2562 %Intel% %i855% = ssigd_alm, PCI\VEN_8086&DEV_3582 %Intel% %i865% = ssigd_alm, PCI\VEN_8086&DEV_2572 %Intel% %i915GD0% = ssigd_nap, PCI\VEN_8086&DEV_2582 %Intel% %i915GD1% = ssigd_nap, PCI\VEN_8086&DEV_2782 %Intel% %i915AL0% = ssigd_nap, PCI\VEN_8086&DEV_2592 %Intel% %i915AL1% = ssigd_nap, PCI\VEN_8086&DEV_2792 %Intel% %i945LP0% = ssigd_nap, PCI\VEN_8086&DEV_2772 %Intel% %i945LP1% = ssigd_nap, PCI\VEN_8086&DEV_2776 %Intel% %i945CT0% = ssigd_nap, PCI\VEN_8086&DEV_27A2 %Intel% %i945CT1% = ssigd_nap, PCI\VEN_8086&DEV_27A6 [....] [Strings] ;---------------------------------------------------------------------- ; Localizable Strings ;---------------------------------------------------------------------- Intel="Intel Corporation" DiskDesc="Embedded Installation" i810="810 Embedded Graphics Controller" i810DC="810DC Embedded Graphics Controller" i810E="810E Embedded Graphics Controller" i815="815 Embedded Graphics Controller" i830m="830M Embedded Graphics Controller" i835="835 Embedded Graphics Controller" i845="845 Embedded Graphics Controller" i855="855 Embedded Graphics Controller" i865="865 Embedded Graphics Controller" i915GD0="915G/915GV/910GL Embedded Graphics Controller Function 0" i915GD1="915G/915GV/910GL Embedded Graphics Controller Function 1" i915AL0="915GM/915GMS/910GML Embedded Graphics Controller Function 0" i915AL1="915GM/915GMS/910GML Embedded Graphics Controller Function 1" i945LP0="945G Embedded Graphics Controller Function 0" i945LP1="945G Embedded Graphics Controller Function 1" i945CT0="945GM Embedded Graphics Controller Function 0" i945CT1="945GM Embedded Graphics Controller Function 1" [....]

Do you mean this driver? https://vintage2000.org/windows/windows_98#intel_945gm_display_driver_for_windows_98

If you mean a Window's DOS box: try "DIR /S" after changing to your USB-drive letter (without quotes). Total used and free space will be shown. BTW can take a LONG time in your case... Screenshot shows my 16MB (virtual) drive (some space is used by directory clusters, not counted):