deomsh

Wave can play uncompressed sound only. Compressed files are decompressed by the player. On Win9x System Sounds are 22050 Hz only: Radio Quality. Maybe the driver has problems switching frequency of your ALC883. How sounds a System Sound with a WAV in CD-quality? Another possibility is playing with the Wave-buffer, I found 5 seconds best (default is 4 seconds). Further: on my system Playback of media-files is best with Direct Sound output (software emulation only). I think thats not possible in case of System Sounds. About pop's and click's: all HDA-codecs are producing them, but most drivers are programmed to switch sound off during the load-phase.

This is not a true statement in general. Two out of three HDA-chipsets I was able to test, worked out-of-the-box (with HDATSR.EXE in AUTOEXEC.BAT). One HDA-chipset needed my quasi-general HDAICOUT.HDA (download on page 8 of the thread mentioned), the file for "Codec Index=$0" (=HDAICOUT.HDA.000). If there is silence only, setting the right "Output Widget" in HDACFG.INI is important - the driver has no a Widget Parser. Sadly there is no list of $-values - could be made if enough serious testers were available. I have fairly good system sounds, maybe because of some heavy tweaking. About using the driver at all: it's written by Watler for Win3x, Stereo-Playback for max 16 bit & 48 KHz only. Installation on Win9x is easy, in case of WinME it's much more complicated (no Real mode). Further: use of this driver can give serious stability problems.

You have to rightclick on ERU.EXE, hold the button and drag to your desktop. Then you can choose "Create shortcut" ,or something like that, in the menu shown by Explorer. Dragging works in Progams too.

@Wunderbar98 Thnx for sharing, nice story. Since Windows 9x uses other configuration files too, I prefer ERU. It came with the Windows 95cd, but its free software and still available (as ERUZIP.EXE). Files backup'd can be edited too in ERU.INF.

@jaclaz Thanks again. I will will thorough test 0E in final testing of Part VII. Although tempting, I have not yet decided to reuse my project for other flavors of Win9x, or try running Windows 3x on a Memdrive. For the time being this project is very time consuming, for now I have to return to final testing of Part V.

Thanks for clarification. I'd run some time-consuming tests with my MBR-aware tools while on the Memdrive. Indeed, Grub4Dos and Win98se doesn't care if the bootcode is made empty. But my USB Legacy BIOS definitely needs the bootstrap code to boot the USB-drive. I've read that post several times during my Part VII-research . Please, can you clarify why my project won't be affected?

@jaclaz Thank´s a lot for elaborating. As far I can judge your first mapping gives same result like mine, only mapped to (hd2). And a corroboration of mine, isn't it. Your second mapping gives a memdrive with two partitions, second active. Give also very interesting testing-possibilities! Grub4Dos readme states (in update 4): "Here win98.img is a partition image without the leading MBR and partition table in it. Surely GRUB for DOS will build an MBR and partition table for the memdrive (hd0)". I admit I could find my desired mapping nowhere, but by trial-and-error it was a very easy job in comparison to other parts of my project. Can you explain the MBR copy-part? The bootcode-part (before partition table) of my MBR-dump of the Memdrive looks different to the original (but I can't read MBR-code).

I just remembered the speedtest was cited on Vogons (don't know why). https://www.vogons.org/viewtopic.php?f=24&t=12102 One of the links should work.

@jumper NN 3.04 is Netscape Navigator 3.04 (16-bit). Runs in Windows 98se too (but NOT with normal internet connection). Conforums is not on Google anymore. Try this one: https://web.archive.org/web/20180413181223/http://win3x.conforums.com/index.cgi?board=net&num=1517876379&action=display&start=49

@jumper If you found my sentence hard to understand, see correction above. In case you are interested in the test, see: https://web.archive.org/web/2018*/http://win3x.conforums.com/index.cgi?board=net&num=1517876379&action=display&start=49

@jaclaz Thank´s for posting. I did as you asked. Can´t post pictures anymore, so here is the full screen "written-down" (except txt after hex). Not sure if you only want the partition-table of the Memdrive. I can upload full MBR-dump's of the Memdrive and/or the USB-bootdrive - if needed. Booting command-list Found 1 USB devices. Device Num: 0x80; floppies_orig=0, harddrives_org=1, floppies_curr=1, harddrives_curr=1 FAT32 BPB found with 0xEB (jmp) leading to the bootsector probed C/H/S = 64/255/63, probed total sectors = 1028160 00000001BE: 80 01 01 00 0C 01 01 40 3F 00 00 00 41 B0 0F 00 ; 00000001CE: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ; 00000001DE: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ; 00000001EE: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ; 00000001FE: 55 AA ; Can you elaborate please what you ment with your comment: "maps the first (primary) partition to the whole device (i.e. it should be a superfloppy), unless there is something else going on , the (hd0,0) reference should not be valid. It should be: map --mem (hd0)+1 (hd0) to map the whole disk." I am afraid I don't see the problem, why "not valid"?

Advantages: 1) Changing User Agent, custom and with presets. 2) Sending real or custom referer (not tested). 3) Cookie Management (not tested). 4) No download problems (speed is not the highest). 5) Still available (in the first half of 2018 I did a speed test with NN 3.04: out of 8 "compatible" tested web proxies, proxycrime is the only one left.

Part IV: Windows 98se on Grub4Dos Memdrive with full USB 2.0 access In this part, after booting Windows on the Memdrive, there will be full access to the USB-bootdrive – mounted as regular USB 2.0. After renaming USB.IN_ back to USB.INF, installation of NUSB 3.3, and adding mbrint13.sys ; Grub4dos to IOS.INI [safelist], the Memdrive should be booted first to “Command prompt only” with changed MENU.LST: ------------------------------ MENU.LST ------------------------------ # comments always BEFORE a command title Boot IO.SYS chainloader (hd0)+1 rootnoverify (hd0) title Win98se on Memdrive with USB 2.0 access # only one USB-drive allowed during boot errorcheck off # "usb --init" is not ment to be used on an USB-hub (Grub4Dos Readme) usb --init # for one “real” floppie-drive; if needed map (fd0) (fd1) map (fd1) (fd0) # USB-bootdrive (hd0)should be “outmapped” by Memdrive map --mem (hd0,0)+1 (hd0) map --hook # without second mapping 3½” floppie can be seen as 5¼” by Explorer; if needed map (fd1) (fd0) map (fd0) (fd1) map --rehook # mandatory, without changed UUID “open files blue screen” while mounting USB boot-partition # USB boot-partition not visible from “Command prompt only” anymore uuid --write (hd0,0) B00D-1D20 vol --write (hd0,0) U20MEMDRIVE # not critical, for other possibilities see Jaclaz 09-22-2017: # https://msfn.org/board/topic/177102-solved-as-is-windows-95-issues-with-grub4dos/?do=findComment&comment=1145058 root (hd0,0) chainloader /io.sys title Reboot IO.SYS on Memdrive uuid --write (hd0,0) B01D-1D20 vol --write (hd0,0) R20MEMDRIVE # critical, otherwise Memdrive can be rebooted only once (experimental) root (hd0,0) chainloader /io.sys ------------------------------ After booting Windows on the Memdrive, all USB-Controllers and already attached USB-Devices can be installed in Device Manager. If not there yet: SYSTRAY can be started from START --> RUN. All changes can be copied “down” to the Windows USB boot-partition. It should be possible to remove the USB 2.0-bootdrive, or insert it again, in the normal way. Without Memdrive, Windows can only be started in Normal Mode after disabling USB-Controllers (in Safe mode, or with a REG-file from “Command prompt only” before booting Windows). See attached REG-file as example (machine-specific). USBCTLNO.REG To enable USB-controllers again, following REG-file has to be imported in the Registry before booting Windows on the Memdrive. Example in attached Reg-file (machine-specific). USBCTLYS.REG Importing REG-files can be automated with attached batch-file (together with batch-commands for one logical drive already). USB20.BAT BTW: After booting Windows on the Memdrive, it’s important - according to my experience - to wait ALWAYS before starting any program until Mouse’ Hour-Glass has been vanished. Also it’s a good habit to run Scandisk before copying anything from the Memdrive back to the USB boot-partition. BTW2: Max 400-500MB, more space with Drivespace and/or logical partition (fixed drive-letter for logical partition on Memdrive has to be obtained with Device Manager). BTW3: If no CD/DVD-drive available, Windows 98se files should be copied to USB-bootdrive before. Other possibility: at least all files mentioned in in USB.INF, MSMOUSE.INF and KEYBOARD.INF has to be copied to their destination first. Afterwards they can be skipped ("missing files" installation-dialog). USB-Mouse/Keyboard is not available during installation of USB-Controllers (one PS/2 Input-Device should be available during install).

I am using http://proxycrime.com as last resort. See my post of april, 23 thread posted in next post by @Goodmaneuver

Part III: Windows 98se with PCI-devices (except USB) on legacy USB 1.1 In Part I detection of PCI-Bus is omitted, but not disabled: MSDET.INF hasn’t changed. Part III continues the installation of Part I. Full installation will be accomplished in Part IV. After renaming USB.INF to USB.IN_, PCI-Bus and dependant PCI-devices can be installed with Wizard New Hardware, no reboot in between. Before final reboot, Standard VGA must be deleted in Device Manager; all USB-Controllers should have yellow exclamation-marks. BTW: The Part III installation can be run from a “Part II”-Memdrive. Same method, same limitations.

@jaclaz Thanks a lot for your efforts! The results of a few dozen experiments are suggesting that you are right with the attribute-"thing" I did some new tests with help of my old Diskedit, with maybe conclusive results, at least on my system (don't try this at home......). On a newly FAT32-partitioned 4GB USB-drive with only one primary partition, I wrote a volume-label with MS-DOS 7.1 LABEL.EXE. This gave the volume-label as first Directory-entry with attributes A - - - V and date and time of writing. The volume-label was further written to the Bootrecord in Sector 0 and to the Backup-bootrecord in sector 6. Changing volume-label in Bootsector after erasing in Directory was useless, no output from MS-DOS 7.1 VOL, DIR, LABEL.EXE and FDISK.EXE anymore. Grub4Dos gave with vol (hd0,0) following output: "(unsupported)". Writing volume-label with vol --write (hd0,0) GRUBDOSNAME gave this volume-label as second Directory-entry only, with attributes - - - - V and as date 0-00-80 (whole entry is marked "RED" by Diskedit, but okay after writing a valid date). Output of vol (hd0,0) was still GRUBDOSNAME In MS-DOS 7.1 VOL, DIR, LABEL.EXE and FDISK.EXE displayed all the first volume-label written by LABEL.EXE. As soon this volume-label was erased by setting first byte to E5, they displayed all the second label written by Grub4Dos. Rewriting the volume-label with LABEL.EXE erased the label written by Grub4Dos, LABEL.EXE set first byte to E5. Grub4Dos showed this label as sRUBDOSNAME (Greek 's', can´t show it in this post) and was willing to write a new volume-label. Deleting volume-label with LABEL.EXE erased both, and the directory-entries were overwritten after copying files to the drive. On my 1GB FAT16 USB-FDD: same results, although I am not fully sure if LABEL.EXE erases the second volume-label if it´s on an other sector of the Root-directory. Tired of testing I never ran into problems while using Partition Magic 5.01 because this program write volume-labels without the Archive-attribute! I hope you are confident now with my comment "# vol --write not compatible with labels written by FORMAT or LABEL", presumably the MS-DOS 7.1 one´s - the post is about Windows 98

@jaclaz My comment about LABEL and Grub4Dos was not ment to discuss this fabulous program. I have only some experimental findings to offer. I just repeated them on a FAT16 USB-FDD made by RMPREPUSB, and a FAT32 USB-HDD partitioned with FDISK (BHDD-version) and formatted with FORMAT (no system). It's sad I have reached my 350KB file limit, so I can't give any pictures. With cat --hex (fd0)0+1 there is actually a name in the bootsector. With cat --hex (hd0)0+1 not, but with cat --hex (hd0,0)0+1 too. I can't change these volume names with Grub4Dos. After deleting the volume names with LABEL.EXE, the bootsectors say NO NAME (and so does PTEDIT.EXE for the USB-HDD). If I write vol --write (hd0,0) VOLGRUBOKE? (or with (fd0)), VOL is displaying this happily in MS-DOS, but the bootsector is still NO NAME. If try to write the same volume name with LABEL.EXE, the "?"-character is refused, luckily VOLGRUBOKE! is accepted. BTW: thanks for your old post, interesting stuff!

@jaclaz About changing label of Memdrive: it's not needed for a batchfile, just to gave the C-drive a nice name in Explorer My boot-drive is named USBPRIMARY1, and is the D-drive after booting the Windows on the Memdrive. About LABEL: I am used to partition my USB-drives with Partition Magic 5.01. The "vol --write"-command never gave any problems and I used it in earlier versions of Part II. The command didn't work anymore for renaming a Drivespace Host-drive, and too when I formatted an USB-drive with FORMAT. Same story with LABEL.EXE. If the label is deleted by LABEL.EXE, the "vol --write"-command is working again. In PTEDIT.EXE can be seen that the "vol --write"-command is not writing to the FAT, while LABEL does. Also labels written by Mini-Tool-Partition Magic and RMPREPUSB I found not compatible with the "vol --write"-command of Grub4Dos. As a workaround I first used "cat", but rewriting UUID is much easier in my opinion. About my floppie-mappings: without mapping I have simply no acces to A: or B: from the Memdrive, only with mapping. With the first two mappings Drive-letters are reversed, with last two mappings everything is back to nomal. My built-in Floppie-station is now always A: and an attached USB-FDD always B: Hard-drives gave no problems after booting the Memdrive.

Part II: Quasi-universal Windows 98se on Grub4Dos Memdrive with full Legacy USB 1.1 access The “Part I”-installation can be run from a Grub4Dos Memdrive and with full access to the USB-boot-partition and with changing UUID of the Memdrive (experimental). In my experience Windows will only boot from a Memdrive with HIMEMX.EXE and without HSFLOP.PDR (or disabling floppy-controller; also DRV*.vxd’s can give problems). Memdrive will be max 400-500MB, mainly depending on drivers and vcache. I used [vcache] MinFileCache=1024 and MaxFileCache=1024 during experimenting. GRUB.EXE (0.4.6.a) can be started from real MS-DOS with following MENU.LST: ------------------------------ MENU.LST ------------------------------ # comments always BEFORE a command title Boot IO.SYS chainloader (hd0)+1 rootnoverify (hd0) title Memdrive with Legacy USB 1.1 access # with, or without existing second disk errorcheck off map (hd1) (hd) # mapped USB-bootdrive becomes always second disk map (hd0) (hd1) # needed for possible use of floppy drive map (fd0) (fd1) map (fd1) (fd0) # USB boot-partition loaded in memory and mapped as first drive map --mem (hd0,0)+1 (hd0) map --hook map (fd1) (fd0) map (fd0) (fd1) map --rehook # UUID must be different from existing MS-DOS Volume Serial Number # 16 characters available (hex; 0 – not O) uuid --write (hd0,0) B00D-1D11 # vol --write not compatible with labels written by FORMAT or LABEL vol --write (hd0,0) U11MEMDRIVE chainloader (hd0)+1 rootnoverify (hd0) title Reboot IO.SYS on Memdrive chainloader (hd0)+1 rootnoverify (hd0) ------------------------------ More space is possible with Drivespace and/or a logical partition. A logical partition can get a fixed drive-letter with SUBST, but the drive-letter will shift if booting from the Memdrive. SUBST for different drive-letters can be automated with following batch-file, USB11.BAT: ---------------------------------------------------------------------- USB11.BAT ---------------------------------------------------------------------- REM if USBLOGICAL1 label of logical partition REM SMARTDRIVE not in AUTOEXEC.BAT DEL C:\VOLUME*.txt VOL C: > C:\VOLUMEC.txt VOL D: > C:\VOLUMED.txt VOL E: > C:\VOLUMEE.txt FIND "USBLOGICAL1" C:\VOLUMED.TXT if errorlevel 1 GOTO U11MEMDRIVE SMARTDRV /X C+ D+ /B:57344 SUBST X: D:\ GOTO END :U11MEMDRIVE FIND "B00D-1D11" C:\VOLUMEC.TXT if errorlevel 1 GOTO SMARTDRIVE REN C:\WINDOWS\SYSTEM\IOSUBSYS\HSFLOP.PDR HSFLOP.PD_ REN C:\WINDOWS\SYSTEM\IOSUBSYS\DRV*.VXD DRV*.VX_ FIND "USBLOGICAL1" C:\VOLUMEE.TXT if errorlevel 1 GOTO SMARTDRIVE SMARTDRV /X C+ D+ E+ /B:57344 SUBST X: E:\ GOTO END :SMARTDRIVE SMARTDRV /X C+ /B:57344 GOTO END :END ---------------------------------------------------------------------- In case of attached hard-drives, IO.SYS patched with PCHIO is very convenient for collecting drive-letters (part of MDCU, see: http://www.mdgx.com/web.htm ). BTW: BUFFERS shouldn't be set too low, or “Reboot to MS-DOS Mode” from a Memdrive may fail.

Part I: Quasi-universal Windows 98se on Legacy-USB 1.1 Installation of Windows 98se with "SETUP /P I;S=detectbus" (without quotation marks, a space between P and I) skips installation of the PCI-Bus and dependent PCI-devices. Although USB-drives have different speeds, Smartdrive speeds up ALL volumes running in MS-DOS Compatibility mode. I used SMARTDRV /X C+ /B:57344 for highest speed; max partition-size is 128GiB ( according to R. Loew). With my fastest USB-drive BOOTLOG.TXT gives 6 seconds boot-time! BTW: strictly spoken, "/P I" is not needed here, but used for Part III and further on.

Every part of this project is one out of (almost) nine ways to run Windows 98se from an USB-drive. Two parts are about the Windows 98 Second Edition installation using the legacy USB-connection. The other parts are dependent on Grub4Dos. Each part gives needed changes in respect to the one before. All installations are possible in directory C:\WINDOWS: no drive-letter assignment needed. Needed for the first eight parts: · Legacy BIOS must be USB-HDD compatible. · 512MB RAM (reasonable minimum). · 500MB USB-drive (reasonable minimum). · Partitioned USB-drive (USB-HDD). I am not sure if anything I did is new, but you will let me know. In retrospective everything is easygoing, although later parts and project extensions are more complicated. Except Grub4dos, everything is experimental and (almost) undocumented. The results of the project are divided into following parts: Part I: Quasi-universal Windows 98se on Legacy-USB 1.1 Part II: Quasi-universal Windows 98se on Grub4Dos Memdrive with full Legacy USB 1.1 access Part III: Windows 98se with PCI-devices (except USB) on legacy USB 1.1 Part IV: Windows 98se on Grub4Dos Memdrive with full USB 2.0 access Part V: Windows 98se on USB 2.0 with Grub4Dos Memdrive as bootchain Part VI: Windows 98se from a logical partition on Grub4Dos Memdrive Part VII: Installation of Windows 98se on a logical partition with Grub4Dos Part VIII: Windows 98se on other USB 2.0 partition with Grub4Dos Memdrive as bootchain Part 8½: Full installation of Windows 98se on an empty Grub4Dos Memdrive without rebooting Concluding remarks DISCLAIMER: THIS PROJECT IS POTENTIALLY ADDICTIVE, I DON’T PAY FOR REHAB!

This is my workaround, together with Total Commander for Android (free!). Using an USB-drive with normal and with micro-USB-connection. BTW: not all smartphones can mount an USB-drive!

Is duckduckgo not working in Dillo?

Please read this: https://msfn.org/board/topic/157173-kext-diy-kernelex-extensions/page/25/#comments MSVCR70.DLL or MSVCR71.DLL should be used instead of MSVCRT.DLL too. Rename/ copy when still in MS-DOS (real mode) or use KnownDLLs in Registry (reboot needed).

Already tried this fix? https://web.archive.org/web/20060314222520/https://www.tweaktown.com/guides/68/agp4x_via_chipsets_fix/index.html