LLXX

You are advised to carefully read http://www.msfn.org/board/index.php?showto...927&hl=pcss for more information on INF files.

Did a manual inspection, seems to be the genuine disk-labeling utility. The question is, why was it running as a service? Either way, you can safely remove its entry from the service table.

Read the Ghost documentation for how to use it.

Generic ("ESMT") DDR400, overclocked to 533 with +20% voltage increase.

I just found out the Windows 3.11 DDK (Driver Development Kit) contains the complete source code of the WDCTRL.386 HDD driver. This should make it easy to implement some new features (Google "Windows 3.11 ddk" to find the download.)

When programming, you should always use "round" numbers, i.e. powers of 2. Reading the file in 32768 byte blocks would solve the problem, though I recommend 65536 since you will get better performance (approximately twice) without excessive memory usage. The reason is, MD5 processes data in 64-byte (512 bit) blocks. 30000 is NOT divisible by 64, whereas every power of 2 greater than 64 is. BTW, 30Kb is not 30000 bytes, it's 30720. Edit: You should always see if someone else has already written what you're trying to accomplish, and probably written it better as well. http://md5deep.sourceforge.net/

You could extract all the contents of the CABs, replace files with updated ones, remove unneeded files (e.g. online services crap) and then repack, then edit the INFs to create a truly custom install.

What's next... Windows 3.11? I think it had its own direct-access (32-bit mode) HDD driver...BTW, DOS 7.1 *does* support 48bitLBA via Int13x.

Most definitely. Folders that can't be deleted nor accessed certainly point to a filesystem problem. I would also suggest a surface scan of the drive, physical degradation of the platters may have taken place.

Worst thing to do is trying to read the whole file into memory at a time, because the file could be huge. Read e.g. 65536 bytes at a time into a buffer, process those bytes, then continue reading in 64k blocks until EoF is reached. I think you're already nearing the limits of VB as a language itself, may be time to move on to C/C++. Type MDxSum dwSum(3) As Long End Type...and shouldn't that be 4, not 3? Also, how the program crashes is important also in figuring out the error. (Invalid Page Fault, Access Violation, Illegal Instruction, etc.)

For example take Armadillo which is very popular and supposedly "excellent" protection:1. size Armadillo 3.70a packed calc.exe with all options enabled (extensive enough?) Original size 92Kb "Packed" size: 'dillo stub 393Kb + packed data 64Kb = 457Kb 2. speed DebugBlocker/CopyMemII + Nanomites + Code Splicing DebugBlocker adds extra process CopyMemII utilises pagefaults (incremental unpacking concept) Nanomites utilises interrupts Code Splicing = extra jumps = increased execution time Someone should pack Prime95 with 'dillo maximum protection and compare results with unpacked 3. buggy? Some programs will not work correctly after being packed. Armadillo is usually reliable though. Some packers are worse, those using ring-0 drivers are the most intrusive. Can be unpacked in 5 minutes. Effort spent trying to "protect" software can be better spent making the software itself better. Trying to make it "exceedingly difficult" for the cracker is also going to make it "exceedingly difficult" for the programmer, even more so. It's very easy, just "protect" a 0-byte file. No impact on usability or performance, because there was none to begin with

4.00.1119 for Windows 95OSR2+ is now available. Comments, test results, etc. are welcome

You may be infected with a trojan. Compress the label.exe and upload it, I can do a further inspection to see if any other files are related to it.

It depends on the driver. Most of the newer ones should be fine. The best way is to do the test - copy 137+ Gb of data to the drive and see if any corruption happens.

http://support.microsoft.com/default.aspx?...kb;en-us;158474 Found via http://www.google.ca/search?hl=en&ie=I...tions&meta=

Installed drivers?

Tell Micro$oft about it.

@erpdude8, see above. I also happen to be using 4.10.2222, the original Win98SE driver with no problems. 4.00.1119 is coming, there are just so many changes between these versions that I can't just copy+paste in a hex editor like I did with the 222*.

It would not be difficult to write a short code that sets the registers appropriately, and is called from AUTOEXEC.BAT while in DOS mode (before Windows loads).

4.00.1111 for Windows 95 OSR2+ is now available for download. 4.00.1119 should be ready soon. Maybe my new code is just more efficient...

This is what I use too. Uses much less RAM and CPU than any other media player I've tried, since ActiveMovie was originally designed to be embedded in another document.

Your hard drive is probably physically damaged. You can use an adapter to connect it to a standard IDE interface on another computer.

It looks like the filesystem was corrupted.

This was my first idea, just unplug and remove the keyb and mouse.

Why even have scripting on in the first place - just disable it. The ads will be gone, any drive-by-download attacks will be unsuccessful, and sites can no longer mess with your browser e.g. changing the window size, disabling toolbars and right-click, etc.