Sfor

I've sent the IP, but I do not know if just one IP will be enough. As, I do not know how the DNS servers of my Internrt services provider are working. Also, I'm curious, if I will be able to receive E-Mail notifications.

The old problem is back, I suppose. I have to use the proxy server, again. Is it really necesary to block the whole country IP range?

It doesn't seem to be working in my case. All I can see is something like an error message with just one word "Arial" in it. But, I did not try the KernelEX, yet.

What particular driver kit do you have on your mind? Also, I've noticed the DOS mode Ethernet driver I've used so far has an importand disadvantage. When the CPU gets hoter, the network speed gets slower. Apparently, the CPU speed goes down, when it gets hoter. Since the DOS mode driver consumes a lot of CPU power, the network speed is affected as well. Funny thing is the problem is visible with the inbound traffic, only. The outbound traffic seems to be working as usual.

Well. The program works. But, a batch made that way is hardly a portable one. Also, I made my own program in Borland Pascal. The resulting EXE file is just a half size of a COM made by C compler. Program Beep; uses CRT; var Tone,Duration: Word; Check: Integer; begin if ParamCount<=2 then begin Writeln; Writeln ('BEEP Frequency Duration'); Writeln; Writeln (' Frequency - Hz'); Writeln (' Duration - mS'); Writeln; Tone:=800; Duration:=1000; end else begin VAL (ParamStr(1),Tone,Check); VAL (ParamStr(2),Duration,Check); end; Sound (Tone); Delay (Duration); NoSound; end.

I wouldn't say it is a ding.wav like sound. It's rather the sound generated when a wrong key is pressed. It's more a tick than a soud. So, it's hardly audible and hardly useful.

It says the application performed an illegal operation (or something like that, since I'm working with a polish version of Windows 98).

I've been trying to make a beep by using batch file in a DOS window of 95/98 system. All I could get was a very short sound same as the Windows error condition sound. Without GUI everything is working as it should to, but in DOS window the PC Speaker sounds are less than audible.

The Go-OO 2.4 OpenOffice release does support the Microsoft XML formats from the package, and it works in Windows 98 without the KernelEX.

I've been told by the support stuff member, their qualified certificates will not work on Windows 98, because of some fault in the system verification procedures. On the other hand qualified certificates from a different authority are working correctly. I've tested the same certificate is not verified correctly on Windows 98, while everything works fine on Windows 2000. I would like to know, what differences in the certificate verification systems are in Windows 98 and 2000? And possibly, if there is some way to make Windows 98 certificate verification services to work the same way as in Windows 2000. --------------------- I have found some informations the problem is related to UTF8 coding problems in Windows 98.

The newest ffdshow codec does not support Windows 98, any more. The status should be changed from ONGD to LAST.

I can not remind the Pablo, while the Gape nick name is still in use. After posting a few comments about Unofficial Service Pack Plus, I tried to keep away from the flames. There was no point in arguing with people preferring quantity over the quality, I believe.

Well, that's not the case. There is another version of the Windows 98 Unofficial Service Pack made by a small group of polish people (I would rather say teenagers because of their language habbits). The core of their distribution is the good old USP 2.1 from Gape. They added some themes, utilities and made some improvements through resource editing. Then presented their creation as USP 4.x So, they are Windows 98 fans, as well. But, they do not like the MSFN, as their creation got significant amount of bad opinions here. The term "Windows 98 USP wars" is my own name of the USP related flame war. Apparently, the changes introduced in the "new" polish USP edition were not considered as significanly usable by the majority of the local community. The Gape refused to include the changes in his package, as well. The flame war was suppressed by moderators, as far as I remember.

The 137GB barrier is very real on many 9x systems because esdi506.pdr, the FAT32 filesystem driver, has a bug in it. If you attempt to write above 137GB on an unpatched system you'll crush the data at the beginning of the disk. As for the 32GB barrier in Win95 I dunno because I am not knowledgeable enough with 95 but BenoitRen will be able to tell us probably if you are right or wrong. There is no 32GB limit in Windows 95. I've been running a Windows 95 OSR 2 on a 60GB HDD without any problems. On the other hand I had data corrupted, when I switched to 160GB hdd. Since there were no 137GB patch available then I had to switch to Windows 98 + Intel Application Accelerator driver.

I'm do not have any proof, but the whole case seems to be related to Windows 98 Unofficial Service Pack wars.

Windows 95 USB support is very limited. There are almost no USB devices able to work in Windows 95. So, if USB is to be used, Windows 98 is the right choice.

Yes, the LAN I'm accessing the MSFN from does have a static IP, indeed. But, It looks like everything started to work correcly, again.

The MSFN related DNS queries stopped working again. So, I can safely assume the attack from the Polish IP space was made, again. Perhaps I could be of some assistance with legal actions against the attacker. But, the first thing to do would be to find out what company is the the Internet access service provider of the attacker.

The largest Internet access services provider in poland is TP. Their main offer is ADSL with dynamic IP. The TP keeps track of what IP was used by whom in what time period, so it is possible to track a "villain" down and prosecute accordingly. The TP has a right to disconnect the user violating the law, as well. By knowing the IP used it should be possible to track down the provider and perhaps the country region, as TP does use different IP ranges for them. Perhaps, an official investigation will be the most effective tool to get the "punk" stopped.

The next thing to check would be: - Is there a "Atheros L2 Fast Ethernet Adapter" entry present in the Device Manager? - There should be also one or two PCI Ethernet Controller entries present in the Device manager. They should be marked as switched off, or without a correct driver installed. If they are missing it means network card is disabled in the BIOS settings. - What is the contents of the protocol.ini file in the WINDOWS directory?

I've noticed the network file sharing functions are working extremely slow. It is many times faster to transfer files using EEE PC as a client, than server. It is caused by the DOS mode LAN driver, probably. Apparently, network drive sharing requests from a DOS mode driver are processed very slowly.

In theory the NDIS driver setup procedure should add a correct AUTOEXEC.BAT entry by itself. If nothing went wrong, there should be a "C:\WINDOWS\net start" entry in the AUTOEXEC.BAT.

For about a moth, I'm unable to enter the msfn.org. I've tried different DNS servers with the same results. The same problem exists from many locations and different Internet services providers. I can access the msfn.org by using US proxy server, only. I'm starting to believe the whole Poland is affected.

The Windows 98 on my old Asus EEE PC 900 was made quite long ago with many small steps. Now, I've got to do the same in the best possible order. Since the Windows 98 setup did not detected ACPI, it would be good to enable ACPI on as early stage as possible. The problem is the old and proven ACPI enabling procedure does not seem to be working. And I do not know why. Some things have to be installed first, probably. The ACPI support enabling procedure requires to reinstall all PnP device drivers. So, in order to reduce the time spent on the job, it would be good to do it as the first task.

This is a shortened guide of how to make a dual Xandros/Windows 98 system on an EEE PC while using just the flash drives. Pehaps it will be worth to add more details to it in the future and create a separate thread. Before we begin. Setting up a Windows 98 as a second OS along with factory Xandros Linux on Asus EEE PC is a bit complicated task. There are a few reasons for it. - no built in FDD - no built in CD drive - it is not possible to change Grub OS loader settings from Xandros. The XOSL is a boot manager capable of storing the original MBR in a file and swapping drives when booting. While using the swap drives function it will be possible to boot from a flash drive and then to change the boot drive to the built in drive. So, a FAT32 partition with Windows 98 system files could be booted without destroying the Xandros Grub boot loader, that way. One or two bootable flash or USB HDD drives will be necesary. One drive with SysRescue CD and the other with Windows 98(9x) DOS mode files. (Or one dual boot drive with two partitions). The DOS drive should contain XOSL, Windows 98 setup, SYS.COM and HIMEM.SYS files. And perhaps some DOS file manager (DOS Controller or Norton Commander). Also the XOSL should be installed on the DOS drive (preferably with the Rainish Partition manager). The first thing to do is to upgrade the BIOS, as it works only when the factory partition layout is untouched. It will stop working after the FAT12 partition is deleted. Installation 1. Boot the SysRescueCD and resize the the second EXT3 partition with GParted. The GUI is run through "startx" command. The GParted utility is accessible through context menu on the desktop. GParted has some difficulties with handling FAT32 partitions. It failed in my case. So, other partition manager should be used to make the Windows 98 FAT32 partition. 2. Boot the DOS flash and start Rainish Partition manager from XOSL boot menu. Use (Ctrl-P) on the boot manager screen. Then Delete third FAT12 partition and create a new FAT32 in it's place. 3. Boot the DOS and put Windows 98 system files with SYS command to the new partition. Then copy the Windows 98 setup and HIMEM.SYS files there. (creation of a proper config.sys file could be necesary to make the HIMEM.SYS work). 4. Boot the DOS drive again. This time it will be necesary to add an additional boot option in the XOSL. Select the new FAT32 partition and check the "Swap drives" checkbox. It will make the new partition to be the C drive after booting. Then install the XOSL on the C drive. After a reboot The Xandros boot option will require to boot from the original MBR, while Windows 98 partition can be booted directly. 5. To setup Windows 98 boot the system from the new partition, then use the SETUPCOR.EXE, as the SETUP.EXE will not work on the EEE PC. Also the keyboard and touch pad will stop function after Windows 98 will do PnP devices check. It will be necesary to switch off the computer, when the date and time settings dialog is displayed. Luckily the setup will continu from the same point after booting the Windows 98, again. 6. After finishing the Windows 98 setup, it will be necesary to restore the XOSL and Xandros booting option, as Windows 98 destroyed the MBR OS loader durin the setup. In order to do so: - Boot to the SysRescueCD again. - mount the new FAT32 partition. An examplary commands are: mkdir d mount -t vfat /dev/sda3 d cd d - restore the Grub boot loader from orig_mbr.xcf file using DD DD if=orig_mbr.xcf of=/dev/sda - boot to Windows 98 as it was in the step 4 again and install the XOSL. Now you should be able to boot to Windows 98 and Xandros at will using the XOSL.