Sfor

The quality is good enough, for me. Besides the details are not very important, when reading subtitles. Also, the GOM Player does have a quite effective quality enhancement filters. The real video would suffer significantly after applying the necesary video compression. But, in case of cartoons and anime the result seems to be not a bad one.

Here is a direct link to a .FLL file (62MB): http://content.veoh.com/flash/f/2/v3317692...974a445928955ac You should be able to download it without entering the VEOH www site. It is posible to download .FLV files from the VEOH, as well. It appears the .FLL was used with older video clips. The newer clips are in coded with .FLV. Still, in order to play an .FLL file it is necesary to change the file extension to .FLV.

It appears, the VEOH holds significant amount of video clips. Unfortunatelly, I found no good player able to play VEOH .FLL files on a Windows 98 system. I know about two players able to handle the .FLL files. But, both are not perfect. 1) FLV Player. Well, it seems to be working. But, the hardware requirements are huge (or the player is no good on 1.8 Ghz P4). 2) SMPlayer (with MPlayer). Plays the .FLL files significantly better than the FLVPlayer. But, there are some problems with Windows 98 support, probably. The volume regulation does not work, at all (for an instance). My favourite one is the GOM Player. But, for some reason it is unable to locate a proper codecs for the VEOH .FLL files. Is there a better solution than FLV Player or SMPlayer?

I did some tests of the Explorer lockup problem. Apparently the the browser dll replacement removes just some of the all shell and explorer lockup events. It helps, but it does not remove the problem. Another solution is "Unofficial Explorer Lockups SHELL32.DLL Fix". It does not solve the problem completely, but removes some of the lockups as well. On the other hand, when these two fixes are applied together, the explorer and shell lockups are as good as gone.

But, there are java applications compiled to be working on the 1.6. A good instance is one of the Polish govermental programs. According to documentation java 1.5 is required. But, at some point, a programmer compiled some modules with 1.6 requirement. As the result the application stopped working on java 1.5.

I'm using the RealVNC as well. In my case the biggest problem related to the RealVNC is inability to watch remote DOS full screen mode sessions. It is necesary to switch to windowed mode. Then a remote DOS application can be used.

In case of a LAN ARP poisoning attack Windows 9x systems are difficult to defend against. Static ARP entries are not working as expected. Setting a static entry just makes it not to time out. Such an entry will be overwritten by the attacker, and then it will remain that way. This problem has not been solved, so far. The NT based systems are much better in this case. A static ARP entry will remain as set, ignoring all the ARP poisoning packets. There are trojans poisoning the ARP tables of other LAN computers. They are modyfying the HTML code by adding redirections to spam or dangerous sites. If one computers in the LAN gets infected, other computers can be affected as well. The NT based systems can be easily protected through a static ARP entry for the internet gateway. The 9x computers can not be protected that way.

Since the Sinowall is highly integrated with NT kernel, it seem to be highly unlikely for it to be able to work with DOS based Windows 9x boot sequence. The Sinowall integrates with Windows NT networking functions. Windows 9x seems to be completely different on that plane.

Another possibility is to use GO-OO OpenOffice edition. It both runs on Windows 98 sysems and supports the Microsoft Office 2007 file formats. Yet another possibility is to use OpenOffice.org 3. It can work on Windows 98 with the newest KernelEx.

Indeed, the DrWatson can do it. But, I'm trying to find out what files are oppened, not loaded. In other words, I want to know what files are between oppen and close operations. Perhaps a better question would be: What files were not closed?

I'm looking for a possibility to check what files are oppened in the OS. It would be good to know what application oppened them, but it is not a mandatory function. There is a Microsoft utility available, but it records file operations and it is quite difficult to extract informations what files are oppened in a particular moment. I'm curious, if it would be possible to list all the open file handles, or something like that.

It seems NOPEY's shutdown functions are not working correctly in Windows 98. The "shutdown -force" and "poweroff -force" functions are closing the applications. However, some applications are not closed (with the system shell included), so the system keeps running.

Indeed. Switching back to APM does remove the problem of duplicated USB drive letters. However, the ACPI buttons are a very useful function. I do not want to loose the button function by switching to APM.

The CardWizzard is necesary to use PCMCIA cards in DOS. The Windows 95 OSR2 is able to use PCMCIA without additional software. However the correct drivers could be necesary. The CardWizzard integrates DOS and Windows PCMCIA support. Without need for DOS support the Windows 95 should do on it's own. I do have a Satellite Pro 460CDT. It does not support Card Bus. The Cards Bus cards are not detected, simply. In case of plin PCMCIA none Card Bus cards Windows 95 detects them and prompts for drivers, when necesary.

I've decided to play a bit with the Letter Assigner. The result is it is unable to remove a drive letter. All it can do is to replace it with some other drive letter. So, it is not possible to get rid of a duplicated drive letter problem with the Letter Assigner.

I've been thinking about removing the duplicated USB MS-DOS compatible drive letters from Windows by creating a DOS utility. It should be possible to remove a USB drive letter from the DOS. But, there are a few problems: - Where the Windows takes the DOS drive informations from? (DOS or BIOS) Is it necesary to remove the drive from both BIOS and DOS disk drive devices list? - The DOS support for the USB drives comes with loading IO.SYS, as BIOS does the whole job. So, there is no possibility to remove a driver or something. It would be necesary to undo quite a few things, probably. - Perhaps a boot manager could do the trick of removing the unwanted USB drives. ------------------------------------------- I've tried to hide the partition on the USB drive using XOSL boot manager. It did hide the drive in DOS, and the Windows showed just one drive letter. Unfortunatelly, Windows detected the SD card as an unformatted one. So, this system is useless. Clearly XOSL is hiding partitions through a change in the partition table. The Windows can not access the drive in such a case. It could be possible to enable the partition back, after DOS booted. So, the windows gets a correct partition information, that way. But, it would require to create an application to change the partition of the flash drive. It should be relatively simple, when compared to the task of forcing the DOS to loose the USB drive letter support.

Well, I was able to get rid of the Fiolog.vxd through disabling the Task Monitor in the Msconfig. But, it changed nothing. So, Fiolog.vxd is just a side effect, not the cause. As for the ACPI. I do believe the applications closing and disk buffers emptying are done before using the ACPI functions. So, since the disk operations were not concluded, it seems the ACPI is not the problem.

It appears the system does not shut down correctly when Fiolog.vxd is still present after shutting down the application. Fiolog.vxd File I/O Logging VxD for Application Defrag 4.10.1998 I do not know if a newer version of this file is available. ----------------------- A further investigation revealed the Fiolog.vxd is a part of the Windows Defrag system. It is enough to disable Task Monitor to get rid of the Fiolog.vxd. Now, there is no difference in the VXD list before and after running the application. Since the Fiolog.vxd monitors the file operations it is possible to form a theory, the Windows does not shut down because of unfinished disk operations. Further evidence is the fact the Windows does the Scandisk check after switching the power off, when it stucks at the shutdown screen. The good question is, why there is no problem with the system reboot? What is the difference with unfinished disk operations between power down and reboot procedures?

The BIOS USB drive support can cause the multiple drive letter problem, as well. My Asus EEE PC 900 is a perfect example. One drive letter comes from BIOS and is recognized by the Windows 98 as a MS-DOS mode drive, the other is through the Windows drivers. Switching the BIOS USB support off solves the problem in most cases. But, the Asus EEE PC 900 BIOS does not let to do it.

I've compared all the files versions from the Microft's article with files on my computer. All of them are the same version or newer. So, it looks like the Gape's Unofficial Service Pack 2.1 did install the shutdown suplement, already. I do have the Unofficial Explorer Lockups SHELL32.DLL Fix and browser .DLL fixes installed, as well.

Windows 98 does suffer from many issues related to the system shutdown procedures. This time I would like to gather some informations about possible explanations and/or solutions related to application caused shutdown issues. I've encoutered a few applications causing the system to shut down incorrectly. In the same time there are no problems with system reboots. After running and then closing one of the problem causing applications, the system works correctly. But when powering down, it stops at the shutdown screen. After a forced reeboot the Scandisk is started. The pesky applications do not show any error messages or unhandled exceptions. Without running them, the system powers down correctly. I can replicate the effect on many Windows 98 running computers. All do have polish Windows 98SE USP 2.1, IE 6SP1 installed. One of the pesky applications is the Gothic game. It was localized to the polish language, so I can not be sure other language versions will cause the same symptoms.

Bearwindows helped me again. It is possible to enable the ACPI support in Windows 98. To do so it is necesary to import a following registry settings: REGEDIT4 [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Detect] "ACPIOption"=dword:00000001 Then the "new hardware wizard" will detect the ACPI BIOS. However, there is a catch in it. In my case, enabling ACPI BIOS made the windows detect the built in USB card reader. Now SD cards are both detected by the BIOS USB drive support and the Windows giving two drive letters for a single SD card. It does not seem to be a very important issue, but it is a bit irritating.

I'm working on Windows 98 on a Asus EEE PC 900. It works, but a few features are not available. Graphics: VBEMP9x driver - The native 1024x600 resolution is available. - Some minor DOS window application related issues - No Direct Draw support Chipset: Intel chipset utility. LAN card: Atheros NDIS DOS driver. Wireless: I have not tried this one. Web Camera: Did not tried to use it. Sound: No driver available. Power management: It is possible to enable ACPI - Limited selection of the ACPI button events (no suspend option).

The partition image to restore a Windows 9x system is like using a cannon to kill a fly. To make a copy of the whole system it is enough to copy just two folders WINDOWS and Program Files. Also it is possible to do it in an automated way with XCOPY command. To switch between the main system and the copy it is enough to change the folder names, in such a case. It is also possible to keep multiple system copies on the same partition and to switch between them. http://www.msfn.org/board/lofiversion/index.php/t121287.html

Oooops! The problem with DOS applications was not solved, yet. On the other hand, the system does not hang, as it was with the older driver. When starting a DOS application in a windowed mode the screen contents gets destroyed completely. In order to get back to normal, it is enough to switch the DOS application to full screen, and then back to windowed mode (ALT+ENTER). When starting a DOS application in full screen mode, everything works correctly. So, it is a good idea to keep the _DEFAULT.PIF file forcing DOS application to use full screen as the default mode.