
Sfor
MemberContent Type
Profiles
Forums
Events
Everything posted by Sfor
-
Long time ago I've downloaded Intel Indeo 5.11 codec pack directly from the intel site. The intaller and codecs were working both on Windows 95 and 98. I never used Ligos Indeo codecs, as I have the Intel version installed, still.
-
It happened to me to move the mouse by a point during the right button clicking. So, the safest would be to press the shift, then the context menu key (right click) on the keyboard.
-
Indeed it does work. But, if the cursor is moved after holding down the shift key, right click brings wrong options. So, it is necesary to point hold the shift down, then right click. If by an accident mouse moves by a point, wrong context menu will be displayed.
-
I think the easiest way is to delete the current file extension entry. Then o open a file of the deleted type. Explorer will ask what application you want to open the file with. Choose the right application and enable the checkbox for the explorer to remember the selection.
-
There is no certain answer for your question. You did not said what do you want to do with your computer. And yet more important question is why your computer is not sufficient for you, any more.
-
You should look at the View - Folder Options - File Types in the Windows Explorer window. I had to translate the function names from the Polish language. So, the real English names could be different, I'm afraid.
-
That's strange. According to the 98lite documentation the Windows 98 explorer is replaced by Windows 95 explorer in order to get rid of the IE. Since the explorer is the system shell, the 98lite changes the shell to the one taken from the Windows 95.
-
I'm using IE 6 SP1 with AFP 9,0,47,0. The buttons are working correctly.
-
Archived Flash Players available for testing purposes: http://kb.adobe.com/selfservice/viewConten...6&sliceId=1 The only problem is you have to download all flash player releases in one download. In case of the Flash Player 9 it gives 74.7 MB.
-
The weakest point of the current Windows 9x related projects is the language. It is true the english language is a perfect choice for a community like this one. The problem is the resulting projecs are comming just in english language versions, as well (other languages are rare). More languages will draw more users and more tallented people. A skilled professional will not put an effort to a projest without some benefit to the systems in the vicinity. In my case just a few of the solutions available here can be used by me. I do have some ideas of my own, but the results are just in Polish language, as well. If you want the community to grow, start from making projects multilingual. Such a task will require a lot of cooperation. As the result, the projects with the best multilingual support should become the best around. The first step could be to collect informations about other language support forums related to the Windows 9x systems like this one. It would be much easier to find group of support in a particular language. Also, such a database can strenghten those groups and stimulate flow of ideas between the language borders.
-
The Intel Application Accelerator is not necesary, but it does a few nice things. It prevents windows default IDE driver from destroying data on LBA48 IDE HDD drives, by adding LBA48 support (over 137GB). It enables DMA transfers, as well. The default DialUp connection setting tries to login to the server. In most cases the PPP protocol does it, and additional logging in is not necesary. So, it tries to login, when it is logged in, alresdy. It wastes some time, that way. I'm using a localized Windows version, so I can not say exactly, what is the name of the option. But, you should switch off something called like "login to the network".
-
You need a correct Intel graphics controller driver. Because, the chipset update package does not contain the graphics controller drivers. The intel chipset utility packages are taking care of almost all the chipset related hardware. The exception is network cards and graphics controllers. These drivers are too big to fit in a small chipset utility. It would be a waste of time to download a huge chipset utility for a board without an integrated graphics controller. ---------------------------- Oh here it is: http://downloadcenter.intel.com/Product_Fi...x?ProductID=798
-
98 (FE), 98 SP1, 98 SE + ME SHELL32.DLL fix
Sfor replied to MDGx's topic in Windows 9x Member Projects
Recently, I've tested the Shell32.dll fix with and without the browser DLL fix. Looks like the Shell32.dll does not solve the problem completely. The same goes to the browser DLL fix. But, when both fixes are applied the result seems to be a perfect one. -
I'm using a polish language Windows 98 SE version. The Windows Update from the Start menu is working still.
-
A few facts: - user32.dll has country specific file paths hardcoded. It is not possible to use other language version of user32.dll file. - the LBA 48 path (large HDD support) does not require user32.dll library replacement. - the Microsoft Windows Update site works correctly if the newest java runtime enviroment is not installed. I do not know exactly what JRE versions are disturbing the Microsoft Windows Update, but JRE 6 patch distributed with the Open Office disables the Windows Update system, for sure.
-
It is possible to "personalize" the Windows Update. There is a switch box to add the link to the updates repository library. You will be able to browse the library and to download any updates you want to a folder of your choice.
-
The question is if the BIOS will let you to use the HDD of this size. Some old bioses hanged during detection of such a big drive, others clipped the size of it to the 137GB. With the Intel Application Accelerator you will be able to use the full HDD capacity, even if the BIOS clipped the disk size to 137GB. But if the BIOS is hanging during the drive size detection, you need the BIOS update. It's not a file system limitation, but an OS one. Win9x uses a 32-bit pointer for HDD addresses. Thanks to LLXX' patch, a 48-bit pointer is used. Well, it is not exactly the truth. The problem is with the generic IDE driver. Other large disks (without an IDE interface) will work without any patch. The 32bit pointer limits the size of a single file to 4GB. It has nothing to do with the LBA48 limit. In case of files accessed through the Windows 9x network interface the maximum file size is 2GB, only. Windows 98 can work with a single partition of 400GB and larger. But, the scandisk and some other disk utilities will not work correctly. Also the automatic swap file system can fail, as well. It's a strange one to me. I'm afraid to connect a Windows NT based system directly (without a NAT router) to the Internet. While I have no fear to do the same with Windows 98 (even without any firewall or AV protection). And that is because the Windows 98 does not have any server like security holes. A non IE browser (or a safe browser) is enough to make a Windows 98 computer a secure one.
-
I'm using polish language Windows and IE. So, I can not install every english language update, I'm afraid. The effect I've described happens on certain sites, as well. But in my case the links are oppening without any delay. After closing a child IE window the parrent IE window becomes locked. But, other IE windows started separately are working correctly, in the same time.
-
Well, it is buggy for sure. But, a lot of software depends on IE. Resolving this problem can improve IE dependant software as well.
-
I'm trying to create an empty (0 length) file with a batch script. The biggest problem is the fact DOS, Windows 98 and Windows 2000 do handle such situations differently. Windows 2000 will copy a 0 length file with a copy command. On the other hand the Windows 98 or DOS will display "0 files copied" message in such a case. Windows 98 is able to create an empty file with such a command: if>empty.txt Windows 2000 will just say the > character was unexpected here. I'm trying to find a solution working in DOS, Windows 95, 98 and 2000.
-
After oppening a link in another window through a SHIFT+click, then closing the child window, quite often the parrent window freezes for a while. In most cases the parrent window resumes in less than a minute. I've observed this behavior on many computers with Windows 98 SE USP 2.1a and IE 6 SP1.
-
The Print Screen key support is done in the computer BIOS. So, it is not possible to take advantage of it in the QBasic. Basicaly the Print Screen event is handled by the BIOS before the key press event is reported to the DOS. So, the QBasic is not able to capture the Print Screen key. In order to reroute the print screen key it is necesary to capture BIOS interrupt by own routine. QBasic can not do it. In case if the Windows is working, BIOS does not handle the print screen, any more. As, Windows handles the keyboard events without the BIOS. So, you should not to look for the standard DOS like Print Screen effect in Windows. Windows Print Screen sends the captured data to the system clipboard, instead of printing them. So, you will have to paste the data to a Notepad or Paint, then to print it by yourself.
-
Finally, I had an opportunity to test my theories. The SMC Barricade LPR/LPD driver I was using in the past with 9x systems failed to print to the Konica print server. On the other hand the HP software posted by j7n worked perfectly. Sadly, according to the licence agreement displayed by the HP installer it is not a freeware. So, I'm not sure if I have a right to use it. The conclusion is the standard IP port from Windows XP is something more than a plane LPR/LPD.
-
Install w98 on Large Drives (Above the 137Gb Barrier)
Sfor replied to Fredledingue's topic in Windows 9x/ME
Please read,... then write. -
Install w98 on Large Drives (Above the 137Gb Barrier)
Sfor replied to Fredledingue's topic in Windows 9x/ME
Are you sure? I think that doing so you will have to re-partition the whole drive and erase all datas on it. This even if you just want to add a partition. Or does it depends on the partition/formating utility? The problem is to not let Windows to write anything above the 137GB barrier, before the patch is applied. That's all. So, you can partition the whole drive before the Windows is installed. Or you can englare the first partition with some partition manager (FDisk will certainly not do that) after the LBA48 patch installation. Or you can add more partitions with FDisk, leaving the first one unchanged. Repartitioning does not mean partitioning from the beginning. If the drive does have an unassigned space it is enough to add another partition and format just a newly added one. Changing the size of a partition is another story, because FDisk can not do it. But, still, the reformat and data loss is not necesary. As, there are partition managers able to manipulate partition sizes. The Partition Magic is the most famous one, I believe. But, versions before 7 were not able to handle LBA48 sized hard drives correctly.