awkduck

When I use Rloew's "64bit File System API" I get a similar error. This isn't really a suggested work around, more informational, but I just don't use Explorer. With an alternative shell "like Losi or Blackbox" and Explorer "like 2xExplorer" I can get along just fine. It is actually my preference, even without the error. In this case, it might be good to rename Explorer.exe to Explorer.bak, and create a Explorer.exe.lnk to 2xExplorer.exe. Some people have altered the installation, to included the USB drivers. The process is then automated. You add your USB files to the Windows 98 installation setup folder. The process is the same for any other driver, you want included during setup. I just haven't done it in a long time. I've done it, post install. Depending on the circumstances it is almost trivial, for somewhat experienced users. But I recommend taking the high road. If you only have USB3, then it does not matter. With USB2 support you can also use most USB audio devices, for default sound. Anyway, good luck and congratulations, with your audio success.

Anyone have problems with "EXTREMELY" choppy USB audio. If you click on the tray speaker/volume slider, small parts of the audio adjustment alert space out and play for a really long time. I'm going to take the install, and test it on a different machine (one proven to work with Win98 USB audio); just in case it got broken. Then if the problem persists, I know its not a hardware issue. Edit: As feared, it is not a hardware issue. If I can detect the cause, I'll post it. Wondered if it had to do with trying to use the USB WDM driver, at the same time as the AC97 VXD driver. But after replacing the AC97 VXD, with a WDM driver, the problem was still there. Are there Win98 VXD drivers for AC'97 cards? Especially, when you get to the 2005-2008 machines. I know there are for Win95. Edit:For AC97, it seems that most likely they, the existing VXD drivers, are for Win95; usable on Windows 98 The following happens on multiple machines. Anyone experience this? I've had issues change from a VXD driver to WDM. Suddenly, programs that use "DX audio FX" crash on load (Example, SoundForge 5). Cakewalk 9 (no DX FX) needed to be downgraded to ver 7 on one machine, and 5 on another, or it would also crash. Dxdiag does not even work, unless I also downgrade to DX7. I might be able to stick with the VXD driver, but Steinberg DX-ASIO does not work with drivers in DX emulated mode. But I'm having suspicions that is isn't supposed to be in emulated mode (full DX support). The WDM driver isn't in emulated mode, and works with ASIO4ALL anyway; but the programs with low latency demands are crashing. Other then really bad "live" latency (best 156ms) the VXD driver works great. I know there may not be a lot of Audio/Music people here, but I thought I'd ask just in case.

@jaclaz No, "Super Grub 2 Disk" is the one I was thinking of. Its just been awhile, since I've looked at it. But now that I'm a little refreshed on it, it looks like one could examine it and maybe gain some Grub2 knowledge. This Github folder has many CFG files. Some of it is well commented. Even with all of that, it is still no Grub4dos. I see they have "disable_gfxterm=true"; so theme support would need to be learned elsewhere. [Some video cards cannot load Windows 9x (some NT versions too) graphics, after Grub2's extended graphics mode are loaded.] [An old bug, that was never addressed. The basic Grub2 video mode is fine.] loadfont /boot/grub/unicode.pf2 insmod all_video insmod vbe insmod gfxterm set gfxmode=1023x768x32 terminal_output gfxterm insmod png set theme=/boot/grub/themes/sometheme/theme.txt And if a guy wants explore the grub terminal, "set pager=1" is a must. There is no pause or scroll back, when listing more then fits in a screen. Pager is kinda like "MORE" or "DIR /P". I like that you can mount and boot an ISO/Harddisk IMG (Grub2). But if your not booting Linux, it would need extra help.

I should probably write something up. I've been meaning to. I only use the file that you are never supposed to edit. I never use Grub2 via Linux (install/configure). I've only compiled it on Linux. I don't know why they don't publish documentation, on using GRUB.CFG. I suppose because it is designed against that. But the syntax seems simple enough, once you actually know what it is. The boot core can be built per your needs, which is neat. Having everything managed by the system, aside from a 2nd config file (using almost completely different syntax), seems to be the kinda thing that made people really dislike systemd. There is a fork of Grub2 "Supergrub2". But I haven't looked into it. I think they moved it away from Linux isolation. Development may have ended.

Grub2 will eventually develop beyond usefulness, for the more minority use cases.

I'm guessing you have over 512Mb/1Gb of ram? Rloew is no longer with us, but he created a memory patch. You could revert your SYSTEM.* files, and try the patch. Your runtime error could be the audio driver. Someone else was getting a similar error. If it is the audio driver, you could use USB audio.

In general/normal use case scenarios, I' have to completely agree with you. Grub2 seems limited, in some important ways. At least in ways that matter to me. However, time and time again, I run into odd machines that will not work "completely" with Syslinux or Grub4dos. USB booting (stuck at USB1.1 speeds or no USB boot at all), strange hardware initializing timings, and legacy USB mouse/keyboard not properly releasing. I've had one machine that would not boot from USB using Grub4dos, unless I first initialized Grub2's USB modules. This must have removed the bios issue preventing Grub4dos from working. A different machine worked fine, without the Grub2 USB modules; but would not work if I had the Grub2 USB modules loaded. You can also edit MSRs with Grub2. But as I've said, these are things you would "typically" not be dealing with.

I don't know if you are still working on this, but more information might help. Maybe Damnation's input already helped? What AGP Bios options are available? What VIA chipset is this? Does this machine already have an integrated video device? I've mostly worked with laptops and thinclients, these days. My accelerated video knowledge, with Windows, is on the decline. Pairing your AGP card info, with your VIA AGP chipset info, may help provide some insight. Is this a configuration that already works, with a different installed O.S.? Have you tried older versions of Catalyst (if your device is supported by them)?

Yeah, sometimes the machine just doesn't want to be your friend. After reading the indecent description, I wondered if the "so I boot into DOS, fdisk, delete primary dos partition" was done from the hard disk dos, or Cdrom/Floppy/USB. Not that it would probably made a difference; I'm just trying to pick at something. I don't recall ever using the installed FDISK, to erase itself. 173a might have been using portable boot media, as I always have.

I've noticed the following, in the ATI SMBUS inf file: Does Win98 need this? Or is it irrelevant?

One of the CD ISOs, that works, was made with WinOnCD. Still UCS Level 1 and no Rock Ridge.

genisoimage -J -ucs-level 1 -o test.iso /iso_files This ISO failed to function.

I noticed "Joliet UCS Level-1" on working ISOs. No Rock Ridge . I'll look into creating something.

Here are four ISOs. All failed, but work when copied. All are CD images. FreeDos Live. FreeDos Bonus. ReactOS Live. Aros Live.

I have gotten a CD ISO to work, that didn't before. I'm guessing that the reason it did not work, previously, was because of errors already tampering with the system. EDIT:{Or, I made an assumption.} But it still did not work, from the foreign partition. I had to copy it, which worked without corruption. The still existing copying issue, with larger files, may be related to Rloew's File64. I can't really test it, when his API is disables. Maybe foreign partition to/from FTP. But File64 is not causing the issue with some ISOs working/not working , from foreign partitions. This still remains, with File64 disabled; both CD and DVD images. EDIT:{I guess it has been tested, since the still working DVD ISOs copied fine. That "potentially" clears it up a bit. Now it is just an issue with why some do/don't work, from the foreign partition. If File64 really was the cause, of file copy corruption, then if points back to some ISO specification difference. I'll try to test ISOs, from opensource projects. Likely most will not work, and serve as examples. If I can't find a certain type, then I'll create one, and upload it somewhere. What will be harder, is making/finding one that works. I can't share the ISOs that work; especially here. I don't have the tools that made the original CD/DVD. I do have some of the tools that cloned them. Knowing how to make working ones, might end up being useful. If anyone has D-tool/VirtualCloneDrive, Paragon's NTFS PNTFS.VXD (Thank's SweetLow), and a USB NTFS partition, this could be tested. If others do not have the same problem, then it might even have to do with my NTFS partition's attributes.

You are right. It is PNTFS.VXD.

Eventually, I'll probably try them both. I am using BIO95DRV.VXD. It isn't important that I have access to ISOs, while the foreign formats are active. But, different circumstances are foreseeable. I mainly wanted to point it out, in case someone has a similar issue. Then a probably culprit would be known. I think we are both in agreement about this. I only differ, from your view, a little. I can not state is as fact, yet. Keep in mind, all of these ISO work "normally", on this machine/OS. So there is nothing wrong with them. While the foreign partitions are active, the issue arises; at no "actual" fault due to any ISO specification/format. At a glance, the difference has been mentioned. It may be that, at one time, there was once a specification difference. Perhaps not even an official one. But, specification difference may have nothing to do with. When the foreign partitions are active, I can also not copy these files; they do not copy correctly. This is what, in my opinion, dismisses the "20" issue; since copying the files has nothing to do with ISO formats. The stunning part, is that the issue persists when the foreign partitions are not involve. Just being active on the system is enough. I should examine what does copy over, and compare that to the original. It is also interesting, with the foreign partitions active, that the other ISOs copy and function fine. This would mean there is something about those files. ISO format may be, inadvertently, playing a part. I initially thought is was partition alignment, and that may still be involved. All of my considerations may be too narrow. Something else could be causing the issue; and BIO95DRV.VXD is only partially involved. I also considered hardware disk issues, but all ISO files otherwise work fine. It is also strange, that the issue is only with ISO files. I thought it might be a large file issue. But, one of the working ISOs is over 4Gb. All of this is really back burner for me. What I wanted the files for, is more important to me. There is an innate desire to flesh it all out. But for now, under my own time demands, I just copied the ISO content to folders.

The Volume Label is at "8028" just below the Volume descriptor. -this is not char count accurate, due to font spacing- ...........CD001..Win3 2 SUMVOLLAB ...... ...V!..!V............. ...................... ...................... ............".(......( ........{............. ..<- from here (80BE) to (823D) is "20" -> Vendor Name <- "20" till (832C) Just as an example.

"20" as a space in a string, is okay. That did not prevent loading. It was empty space using "20" or "20,00". Data gap, if you will. Normally found right after offset 8000. Large sections of "20", and sometimes additionally "20,00", around and after the Volume Label. The use of "20" and "20,00" may be irrelevant. It may be related to some format/specification, that just so happened to allow for that. Perhaps just certain ISO/Burner software. It may be possible that the "20" and "20,00" could be fine; but as a coincidence, the only images that worked, didn't have them. I'm guessing I could modify a working ISO, filling some empty chunk with "20"s, and it would still work. Some Vendor strings, of non-woking ISOs, "GEAR CD DVD RECORDIG" and " ULTRAISO". A working one is "Smart Storage, Inc". The "Smart Storage, Inc" ISOs have a much cleaner layout.

This is just a kinda note, in case someone else runs into it. I have NTFS support (Paragon), on Win98. This system has no internal drives, with NTFS. USB drives with NTFS and EXT2/3 are connected and used. When a USB drive "having NTFS/EXT*" is plugged in and active, certain ISO files cannot be used. This is tested with D-Tools and VirtualCloneDrive. I cannot even copy these ISO files. For example, from a network FTP to my FAT32 drive. These ISO files do not copy correctly. Once the NTFS filesystem "or other foreign type" is inactive, everything is back to normal. I took me awhile to figure out the culprit, because the files did not have to be on the foreign filesystem. It only mattered that the file system was active. Some ISO files did work. It did not matter if it was a CD or DVD image; nor the Rock Ridge, Joliet, or UDF type. It had something to do with how empty space was written. In hex, if the empty space was written with "20" or "20,00", the image would not work. If the image used only "00" for empty spaces, it would work; even if stored on the foreign filesystem. I don't know much about ISO structure. There is probably some specification difference. But I don't know what it is. Anyway, it was weird and perplexing.

Users are mostly safe. Especially, since there are legitimate/legal uses, for youtube-dl. The legal battle against this software/code is slow. It is also deplorable. The users don't re-share the content, during the act of capturing it; like with eMule/Bittorrent/Gnutella. It has always been more lucrative to pursue the provider, over the receiver. Youtube-dl should enable ad support, in cooperation with Youtube. It already supports user accounts. Then it is up to the user, to edit out that support. We all have the potential to do the same thing, with any browser. You might even "still" be able to do this with browser plugins.

I'm looking for a FFmpeg release, newer then Sherpya's 2011, compatible with Win98. But, until then, there is LibAV. LibAV is very similar to FFmpeg, as it was a controversial fork. The command names are different, but the arguments/options are close. For example: FFMPEG would be AVCONV (AVCONV -I FILENAME -C:V H264 -C:A COPY FILENAME), and FFPLAY would be AVPLAY. The last version of LibAV, that works with Win98, is 11.3. However, it was not complied with SDL support (AVPLAY). But that can be fixed, without recompiling, by also downloading 10.1. After extracting both archives, enter the 10.1 "bin" folder > rename "AVPLAY.EXE" to AVPSDL.EXE > copy both AVSDL.EXE and SDL.DLL to the 11.3 "bin" folder, and then get ready to dust off your Hex editor. You'll also need a copy of LIBGCC_S_SJLJ-1.DLL placed in the 11.3 "bin" folder. AVSDL.EXE is linked to older LibAV shared libraries. But this is relatively easy to fix, since they are only one version number different. For example, it may ask for AVCODEC-55.DLL, but the new one is AVCODEV-56.DLL. So try to run AVSDL.EXE, then use your editor to search for and rename the missing library (AVCODEC-55.DLL > AVCODEC-56.DLL). There are about five different DLL strings to search/rename. It may not be necessary to rename AVPLAY.EXE to AVSDL.EXE. I've only done that, since I've only been able to test the 11.3 version with a non-accelerated video driver. For me, it only gives a black screen. The modified SDL 10.1 version worked fine. If you are using a 3D card, with proper accelerated drivers, the 11.3 version might work. Still, renaming allows both options. I'm not sure how the 11.3 LibAV compares with the 2011 FFmpeg. The date of the files, in 11.3, vary between late 2014 and early 2015. Sadly, I'm not sure if LibAV can capture the Desktop. The 2011 FFmpeg version came out before the Dshow Desktop Capture source commit. Likely neither can be used for capturing the Desktop to video. I think Mencoder, from Mplayer, can do it. I haven't looked into it yet. VLC can do it, but it is slow. Also, there is Virtualdub. But, it doesn't capture, with my video driver. It seems the FFmpeg/LibAV break, with Win98, happened when people switched to MinGW-w64, for building Win32. If I get around to it, I'll see if I can't budge out a newer FFmpeg or LibAV, with the old MinGW; unless someone points out an already existing one(s).

Excellent! Glad you are the sharing type @SweetLow.

I respect your opinion. If you want to expound on your intrigue, no invitation is required. Not that you have to. As is, it is still amusing.

The are some wires to untangle. Vbemp does have 2D acceleration. And that does make a difference. Some older cards, supporting Win3x, did have 3D acceleration. But those that did not, could still play video. Those old videos you've mentioned, are also encoded is a much less complex codec. They system resources, for playback, are much lower. Also, the quality was pretty low. The redraw demands where much lower. There are modern codecs for Win98+, to a degree. But that does not mean your browser can use them. I "personally" don't know what K-Meleon can and can't do. I know newer versions come with codec downloads. Maybe for systems with different SSE capabilities? But, I don't know if that is of any use to the older version. There is the Ringo Mplayer builds. They are newer. I have yet to get any of them to run. Not that I have tried very hard. So you might have luck there. So it probably isn't fair for me to say, that the last supported Mplayer can't handle modern codecs. Edit: The newest Ringo Mplayer build works fine. Keep in mind, Youtube offers several encode types. Occasionally, I've tried to watch something, with a new low priority encoding(AV-1?), and for whatever reason the typical encode types were not available. In this case, I would have to download the Video/Audio and re-encode it myself. From what I can tell, most videos should still work(h264/AAC-LC). As it is for all of us, that post on upstanding forums. The legality changes from country to country, and more concerns the tool(s) creators and their hosting providers. I haven't heard of a person getting in trouble, for using those tools. But I haven't been looking either. The issue with those tools, is that ads are not included. Additionally, content under copyright can be stored locally. I can not say this is true. I haven't tried. What I can say, is that Vbemp may not be your problem. I can say this, since I've had no problem playing most modern encode types. The issues I have had, are when I cannot select less complex video outputs (like SDL). And that "is" related to Vbemp. If a browser has no option to disable accelerated video, or has no updated codecs, that can be a problem. But my experience here, is related to Chrome/Firefox types on modern systems. I don't know what K-Meleon is doing.