LLXX

This is not correct. Patched ESDI_506.PDR uses extended commands for accessing sectors above 137 GB barrier, if you have smaller disk, no extended commands are used. I think that the assumption that drive bigger than 137 GB will support 48-bit LBA commands is reasonable. Petr I should inspect the code more carefully... but this is from original driver: L_C0000622: C0000622 89 43 08 mov [ebx+8], eax ; store *real* #sectors to read C0000625 EE out dx, al ; Count register C0000626 8A 4B 22 mov cl, [ebx+22h] C0000629 D3 E0 shl eax, cl C000062B 89 43 0C mov [ebx+0Ch], eax ; #bytes needed or #sectors needed C000062E 8B 43 10 mov eax, [ebx+10h] C0000631 8B 8E BB 00 00 00 mov ecx, [esi+0BBh] C0000637 F6 81 03 02 00 00 04 test byte ptr [ecx+203h], 4; LBA_SUPPORT? C000063E 74 32 jz short useCHS ; no, do CHS instead C0000640 A9 00 00 00 F0 test eax, 0F0000000h ; reading past 137Gb? C0000645 75 2B jnz short useCHS ; then use CHS instead (this is the error!) C0000647 66 8B 57 45 mov dx, [edi+45h] ; LBA low (7:0) C000064B EE out dx, al C000064C C1 C8 08 ror eax, 8 C000064F 66 8B 57 47 mov dx, [edi+47h] ; LBA mid (15:8) C0000653 EE out dx, al C0000654 C1 C8 08 ror eax, 8 C0000657 66 8B 57 49 mov dx, [edi+49h] ; LBA high (23:16) C000065B EE out dx, al C000065C 8A C4 mov al, ah ; LBA ultra-high? (31:24) C000065E 8A A6 BA 00 00 00 mov ah, [esi+0BAh] ; device # (0 or 1) C0000664 C0 E4 04 shl ah, 4 C0000667 0A C4 or al, ah ; if greater than 137Gb would interfere with Device number! C0000669 0C E0 or al, 0E0h ; that is why it defaults to CHS for this greater C000066B 66 8B 57 4B mov dx, [edi+4Bh] ; Device register C000066F EE out dx, al C0000670 EB 39 jmp short IssueCommandThis isn't exactly the offending portion but I remember that the driver used the upper byte of the LBA for some other purpose.

Move closer to the router. Wireless tends to be sensitive to small things like atmospheric pressure and humidity. What wireless card are you using?

I recommend FlashGet download manager v1.50 (NOT the newer versions, they tend to consume more memory). Largest file I've downloaded through dial-up was ~730Mb. Average speed 6.2Kb/s.

Look at the product ID. http://wiki.djlizard.net/Product_IDs

Isn't it obvious? There's something wrong with the font file.

Many secure sites (banking, for example) use SSL-encrypted connections, in which case you should be safe.

1. I've heard that the DOS scandisk has been tested on disks up to 512Gb with no problem. 2. Correct. 3. This is because they go through the BIOS, and most BIOSs from 2000+ support the Int13x interface that is compatible with 48-bit LBA. I have not found a DOS FAT32-capable defragger yet. 4. Patched ESDI_506.PDR version of Loew can actually be somewhat dangerous, he does not add any code to check if the drive supports 48-bit LBA, thus the driver may fail if used on a drive that does not support the extended commands. I consider this unacceptable, as I frequently swap drives of various sizes and ages into my system. Having to switch from the 48-bit ESDI_506.PDR back to regular (LBA-24 + CHS) driver *before* the drive swap is an annoyance (may also cause data loss if the drive reacts unexpectedly to the unrecognised commands).

It's controlled by a key in the registry... though since regedit is disabled you'll have to create a .reg file and merge that instead. Don't know about the Time though... have you tried adjusting the settings in the Time/Date control panel applet?

Try using the default font, MS Sans Serif. Also might want to close Explorer, delete TTFCACHE from your windows directory, and restart Explorer.

gifsicle, originally developed for *nix but there is Windows port available. http://www.lcdf.org/gifsicle

I'm working on it... though I'm quite busy and haven't really gotten the uninterrupted time I need to disassemble, analyse, and completely rebuild the driver. Maybe in the summer... but I haven't forgotten about it yet

It seems to depend on the motherboard. I've used 2Gb for three months with no problem, while I've seen others complain that only 1Gb won't work on their system even with the MaxFileCache limiter setting enabled.

Bring your XP CD with you. You might need it to perform a repair install or similar.

What sort of problem exactly is it? I think you can click an option in the error window to view the details, it would be more helpful to provide exactly what error is happening and in what file. The CD might be scratched...

You have basically described the process, edit the BIOS binary and reflash it. For AWARD bios there is a specific utility called MODBIN that can be used for this purpose.

Click harder. I'm using probably the same mouse as you (Microsoft Wheel Mouse Optical) for over 5 years now... haven't had any problems with it yet.

Read through the cabarc docs. I remember seeing an option to specify how the files are to be stored across archives.

Search for BASE5.CAB on your hard drive. The hidclass.sys file is contained within it. 04-23-1999 10:22:00p A--- 23,520 hidclass.sys

You will have to extract all the CAB files, modify, and then repack with spanning option due to the fact that some files occupy more than one of the CABs. A file list will be required during repacking, to maintain the original positions of the files. The CAB maker is a free download from M$: http://support.microsoft.com/?id=310618

If you're getting disconnected, try moving closer to your router and adjusting the antenna. This is more of a problem having to do with the signal strength than the software.

Format C: from a DOS boot floppy or similar before installing the XP... it seems you have an OEM version of the XP.

Edit boot.ini in the root of your boot drive to remove the unneeded entry.

Disable some devices while in safemode. The problem is probably in a driver.

Google "Win32.hlp" file, it's ~13Mb and it is the Win32 API Reference.

Embedded systems controllers are usually not programmed in VB.