Fredledingue

ActiveX inside IE is normaly not able to launch exe files or script files through WSH (wscript.exe). IE doesn't use WSH. It uses its internal script engine, otherwise running exe file through IE would be possible. The default IE setting will prompt a warning yes/no dialog when such ActiveX is running on a webpage. You can change the setting to totaly disable such function. Enabling it without promt however is pure suicide. Maxthon offers diferent level of extra security features such as an ActiveX blocker and OffByOne displays webpages without scripts running at all.

Pixia 4.xx (ONGD - FREE) reportedly not supporting w98, works perfectly on w98. NeoPaint 6.5 (ONGD - $$$$) works on w98 too.

Hi Briton. I'v read everywhere that the 22226 is for IBM laptops and that the 22225 is for all other PC. Moreover I'v applied the patch through installing MDGx's installer and also Gape's uSP. It would be surprising that two w98 Gods ( ) made the same mistake by placing a wrong file in their installer and that by an incredible luck these wrong files work on most computers except mine. But since there is version 222222 around, I'm going to test it, just in case I'm lucky. Maybe you are the right guy after all... Otherwise I'll lay $10 for Loew's path. That's not the end of the world. Happy New Year!

Yes, but what would be the point? The sport here is to run w98se natively on the most modern hardware. Not cheating around. I'd bet $100 that w98 will run on yet-to-be-invented quantum processors which will render dual-core obsolete barabaric technology.

As long as my MoBo and Graphic card stay alive, I'll keep w98se running on them. The MoBo, the Graphic card and the case are the only pieces that remain from the computer I bought 5 years ago. Happy new w98 year!

Thanks for your comments! And happy new year!

I applied r.Loew patch and... it works! I was able to partition the new drive up to 143 Gb (Windows sees it with that much free space) with WD's Datas Lifeguard (utility from WD's website). Something impossible before applying r.Loew's patch. Now, I didn't try to fill the drive with 143 Gb of datas, but the fact that windows sees it as a 143 Gb drive is very promising. (It's just a little bit silly to limit the demo version to 145 Gb because it's unclear whether you effectively broke the 137 Gb barrier if you or the partition utility counts 1 gigabites as 1,024 Mb or as 1,000 Mb, as 1,073,741,824 bytes or 1000,000,000 bytes an so on. One way you are under 137Gb "real", the other way you are not. ) The problem with the ESDI_506.pdr patch from LLMX, is that the Device Manager doesn't see any of the hard drive. Datas Lifeguard, which allows you to format and partition the drive, doesn't detect the drive as a WD one when the patch is installed. Both Device Manager and Datas Lifeguard detect the drive normaly when the original pdr file is restored. But in this case, Datas Lifeguard won't let me use more than 137 Gb.

I mounted the new WD 400Gb drive into the case and set it as primary slave. The primary master is a WD 120 Gb. The BIOS detects the new drive but displays for it a capacity of 136.9 Gb only. Then, I restarted windows. Windows Explorer doesn't see the drive (maybe because it's not formatted - but how do I format a drive that windows doesn't see? I hope to find the solution here, on WD website - ). In the Device Manager, however, it seems to be there because there are two "generic IDE drive TYPE 47". If there is only one hard disc installed there should be only one, I think. Then I ran HDINFO. ===> Surprise! The primary master (the 120 Gb drive) doesn't support 48-bits LBA (and supports everything else) The primary slave (the new 400 Gb drive) supports 48-bits LBA and displays a capacity of 400 Gb (contrary to BIOS)! Then I ran 48LbaChk under plain DOS ===> Second surprise! It says "Your BIOS appears to be 48-bits LBA capable and you have a drive larger than 137 Gb installed". Which is good news. Yet, the problems remain that the BIOS doesn't see more than 136.9 Gb, Windows doesn't see it at all and the ESDI_506.pdr patch still set drive C in compatibility mode. I'm a little bit confused with all these conflicting informations...

Yes, when I restore the original ESDI_506.pdr, the drive(s) work(s) OK. I'v tried to one in LLMX's zip file (Mistakingingly the 22226 version, then 22225.), MDGx's installer and Gape's uSP2 and 3. All put my drives on DOS-compatibility mode. I have this problem since uSP2 was realeased. That's the only file that doesn't fit on my computer. I have a WD 120 GB (real: 111Gb). Before, I had a second 40 Gb drive that is removed now. I'm doing a test with HDINFO, right now to see if my BIOS and MoBo are compatible... Currently the BIOS shows for the drive LBA: ON and 32-bits: ON. It doesn't mention anything about 48-bits. The MoBo is 5 years old.

How do I check wheter my MoBo supports 48-bit LBA? (I don't plan to insntall XP on this machine) Thanks.

HELP! If I install the patch on my computer, Hard disks drives are forced into DOS-compatibility mode. I'm worried because I just bought a 400Gb drive...

Yes, one problem have surfaced: If I install the patch on my computer, Hard disks drives are forced into DOS-compatibility mode. I'm worried because I just bought a 400Gb drive...

Here is the report. What does it tell, Doctor? SMARTUDM - HDD S.M.A.R.T. Viewer 2.00 Copyright © 2001-2003, Sysinfo Lab Copyright © 1997, Michael Radchenko www.sysinfolab.com e-mail: support@sysinfolab.com þ HDD 2 Model: ST340016A þ HDD 2 Size: 38166 Mb (37.27 Gb) þ Location: Primary Slave þ Serial Number: 3HS2NY56 þ Controller Revision: 3.10 þ Buffer Size: 2048.0 kb þ Compatibility: ATA/ATAPI-5 þ PIO Mode Support: 4 þ SW DMA Mode Support: None þ MW DMA Mode Support: 2, Active: None þ UDMA Mode Support: 5 (UltraDMA/100), Active: 5 þ Current AAM Value: 80h (80h recommended) - enabled þ S.M.A.R.T.: [û] disabled þ SMART Self-test: [ ] þ SMART Error Logging: [ ] þ T.E.C. prediction monitoring started at: 28-12-07, 23:58:06 Attribute ID Threshold Value Indicator 1/Month T.E.C. ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ * Raw Read Error Rate 1 34 65 þþþþþþ 0.0 Unknown * Spin Up Time 3 0 70 þþþþþþþ 0.0 Unknown Start/Stop Count 4 20 98 þþþþþþþþþþ 0.0 Unknown * Reallocated Sector Count 5 36 100 þþþþþþþþþþ 0.0 Unknown * Seek Error Rate 7 30 87 þþþþþþþþþ 0.0 Unknown Power On Hours Count 9 0 82 þþþþþþþþ 0.0 Unknown * Spin Retry Count 10 97 100 þþþþþþþþþþ 0.0 Unknown Drive Power Cycle Count 12 20 96 þþþþþþþþþþ 0.0 Unknown Drive Temperature 194 0 18 þþ 0.0 Unknown Hardware ECC recovered 195 0 65 þþþþþþ 0.0 Unknown Current Pending Sector 197 0 100 þþþþþþþþþþ 0.0 Unknown Uncorrectable Sector 198 0 100 þþþþþþþþþþ 0.0 Unknown UltraDMA CRC Error Rate 199 0 200 þþþþþþþþþþ 0.0 Unknown Write Error Rate 200 0 100 þþþþþþþþþþ 0.0 Unknown TA Counter Increased 202 0 100 þþþþþþþþþþ 0.0 Unknown ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ NOTE: "*" means life-critical attribute þ T.E.C. not detected. Attribute ID Threshold Value Worst Raw Type ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ * Raw Read Error Rate 1 34 65 58 0000092279A5h PR ER * Spin Up Time 3 0 70 70 000000000000h Start/Stop Count 4 20 98 98 000000000B95h EC SP * Reallocated Sector Count 5 36 100 100 000000000000h EC SP * Seek Error Rate 7 30 87 60 00001D3CDD39h PR ER Power On Hours Count 9 0 82 82 000000003DF7h EC SP * Spin Retry Count 10 97 100 100 000000000000h EC Drive Power Cycle Count 12 20 96 96 000000001247h EC SP Drive Temperature 194 0 18 52 000000000012h SP Hardware ECC recovered 195 0 65 58 0000092279A5h ER EC Current Pending Sector 197 0 100 100 000000000021h EC Uncorrectable Sector 198 0 100 100 000000000021h EC UltraDMA CRC Error Rate 199 0 200 200 000000000000h PR ER EC SP Write Error Rate 200 0 100 253 000000000000h TA Counter Increased 202 0 100 253 000000000000h EC SP ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ NOTE: "*" means life-critical attribute Attribute types: PR - Performance-related ER - Error rate EC - Events count SP - Self-preserve þ Reallocated Sectors: 0 þ Current Temperature: 18 C þ Drive Power Cycle Count: 4679

I also have occasional failure to start for unkown reasons. For a moment it froze at the middle of autoexec.bat! ? Now this problem is gone, yet still sometimes freezes with the screen totaly black and dos cursor flashing slowly. Ctrl+Alt+Del solves the problem. I never tried to find out why because that's not too often. One day changing the power block solved the problem. Lately I reformated and reinstalled and it was better. On my very fist computer, slaping the case to unblock the HD was the way to go...

Thanks DonDam, There were indeed "crosslinked" files during previous scamdisk checks. As soon as the store reopen, I'll get a new HD. It will be cool to have an extra 250Bg or something... and cope with the 138Gb limit.

Thanks, noguru! My computer is in the cellar staircase, it's cold there but not under 0°C, and surely not under 5°C neither. It's also a WD.

Wierd message while installing MDIE6CU 1.8: What the hell may he be talking about? Many other update boxes were appearing and disapearing at a rapid rate, before, during and after this message was displayed...

EXPLOR98.EXE doesn't install properly - Crashes computer Error message: Error loading explorer.exe. You must reinstal windows. Then the computer shut down. Restoring explore.exe back to the Windows directory allowed the computer to restart under Windows. MDGx: Isn't it possible to have the Windows elements (exe, dll etc) in a zip file to replace them manualy (under DOS) instead of using the reinstaller? TBS, Merry christmas and Happy NewYear!

Updates on Christmas Eve! What a wonderful gift!

Thank you for all your compassion for the dying hardware, especialy on this christmas eve. I have copied about 9 Gb of the most useful datas to the other drive with one error here and there. About 99% of the datas have been saved out. TotalCopy (aka Tcopy) has been of great help copiying the datas bypassing the errors without a crash. Then I disabled the drive from bios. I'll disconnect it as soon as I figure out which one it is in the case. I suppose the one that is cold is the one to remove but the fan and the fresh air blowing to them is so efficient that there is no feelable difference of temperature. Is it bad for hardware to be maintained too cold?

Thanks to all, for your replies. Sysdll I'v got a power outage recently, yet it was still working properly after that. The file allocation table could have been affected, I don't know. Do you think that repeated power outages could physicaly damage the drive? Or it's just bad for the datas? The irony is that I'v bought a power accumulator (Mustek) supposed to provide power for computers during outages: It works when you pull the plug out of the wall, it doesn't when the power shut down from the network. Money in the wind... Anyway... This drive is already over 5 years old. I won't mind buying a new one. Going to disconnect it now.

"D" is my second hard drive which has problem recently exposed. When DMA is enabled on this drive, the computer freezes sometimes, when I try to access files on it. Running scandisk under Windows froze the machine as well. Running scandisk under DOS showed "Scandisk encountered a data error while reading FAT on Drive D. This prevents ScanDisk from fixing this drive. [Exit]" Then I disabled DMA, and scandisk seemed to work under Windows. It took about one hour to scan the first 70,000 clusters, then 2 hours to do 500,000 clusters, out of 1,200,000. I stopped the process at about half the cluster scan because it was too late in the evening. I will re run the check tomorrow fully. Here is the ScanDisk.log: Can someone tell me what "Error was partially corrected " means? And if I should buy a new Hard Disc ASAP, before the datas on it became totaly lost. I still didn't try to read files on this drive by fear of crashing my PC. Thanks for your help.

No, I forgot last time I reinstall windows. :oops: (sometimes forgetting happens) Thanks! DMA fixed the problem with the large avi video files, but not with the wma video. The wma video resolution is 738/520... but my processor is a 1.8 Ghz... I don't know if it's normal that it's still choppy. Now this DMA stuff exposed a hard disk problem, which is not or less visible when disabled. (See other thread)

Hi, I need help: I can play every kind of video files however, in some case, playback is choppy. The problem appeared since I completely reinstalled my computer. While the PC run faster for certain tasks, video playing has been disapointing for unexplained reasons. Unexplained because I installed roughly the same softwares as before and the hardware hasn't changed except for the updates. -WMV videos of high definition, like 640/480, don't play smoothly -AVI videos encoded with Asus2 codex (use with Asus graphic card video capture - sort of mpeg2 variant) utter a buzz and freeze one second every 3 or 4 seconds. The videos are recorded properly because once converted to DivX, it's good. I never had this problem before. Updates include uSP3-beta and various updates listed by MDGx since, DirectX9 and WMV9. I have FFDshow installed and whether I use it or not doesn't affect the result. Using different video player didn't help. I didn't try other codex but it's clear that some video settings but everything I tried, any visible setting didn't help.

Sure! All this is very easy -LOL- [everybody know it].