rloew

My API Hook Tool DLLHOOK has been updated to support KernelEx 4.5.2. I have been developing a KernelEx specific addon called KEXEX that contains a DLL with functions I have implemented and an .INI File with redirects for these functions and numerous others that have to be forwarded to new names and/or Modules.

I have noticed similar things in my Computers. I assume it has to do with the way the BIOS allocates Memory Mapped I/O Space. My ECS Computer dropped from 3647MiB to 3071 MiB when I installed a new video card.

WDMEX.VXD is a work in progress. The following additional functions are provided beyond the latest version of WDMSTUB: New Functions: ExExtendZone ExInitializeZone ExInterlockedExtendZone ExInterlockedFlushSList InitSafeBootMode IoAttachDeviceToDeviceStackSafe IoRequestDeviceEject KeBugCheck KeReadStateEvent MmHighestUserAddress MmIsAddressValid RtlAnsiCharToUnicodeChar RtlClearAllBits RtlFindLeastSignificantBit RtlNumberOfSetBits RtlUpcaseUnicodeString ZwDeleteValueKey _purecall _vsnwprintf _allmul ---Stubbed ExUuidCreate IoDeviceObjectType KeEnterCriticalSection KeLeaveCriticalSection KeQueryActiveProcessors SeExports SeSinglePrivilegeCheck KeAcquireSpinLockRaiseToSynch KeLowerIrql KeRaiseIrql KeRaiseIrqlToDpcLevel KfRaiseIrqlToDpcLevel New Stubs: ExUuidCreate IoDeviceObjectType KeEnterCriticalSection KeLeaveCriticalSection KeQueryActiveProcessors SeExports SeSinglePrivilegeCheck RtlAbsoluteToSelfRelativeSD RtlAddAccessAllowedAce RtlCreateSecurityDescriptor RtlGetDaclSecurityDescriptor RtlGetGroupSecurityDescriptor RtlGetOwnerSecurityDescriptor RtlGetSaclSecurityDescriptor RtlLengthSecurityDescriptor RtlLengthSid RtlSetDaclSecurityDescriptor SeCaptureSecurityDescriptor ZwSetSecurityObject ObOpenObjectByPointer Replaced Stub with Implementation: RtlInt64ToUnicodeString Fixed: RtlUlonglongByteSwap Upgraded existing Function in Windows 98: IoAllocateDriverObjectExtension PsCreateSystemThread ObReferenceObjectByHandle

I have used USB Composite Devices such as USB Headsets. I don't have any USB KVM Devices, so I have not encountered any problems so far with using USBHUB.SYS. I wasn't referring to NUSB when I mentioned my WDMEX.VXD Driver. I know WDMSTUB can handle it. I was referring to the fact that WDMEX can handle ALL Windows ME Kernel Functions unlike WDMSTUB. My post was to make the point that I use the minimum of software from other OSes, and then only if it provides useful features that I cannot obtain otherwise. It was not a specific set of recommendations as people's needs can vary.

I do 68K Assembly as well as C. I did a CDROM Driver for the Amiga Computer as well as extend their existing Filesystems.

I use the Windows ME SCANDISK/DEFRAG Files because they handle larger Partitions. I use some of the Windows ME USB Files because they handle more devices such as U3 Keys. Even then I only use the minimum number of them. I do not use USBCCGP.SYS. USBHUB.SYS can replace it. The USB 2 Stack is of obvious value. My WDMEX.VXD extension to NTKERN.VXD can handle all Windows ME Functions required by any new Drivers. NOTHING ELSE !!!

The problem may be related to your inability to shutdown properly. Some data may not be saved in the Registry. Try disabling or uninstalling your Nvidia Driver, rebooting, making your folder changes, rebooting, then restoring your Video Driver.

A few years ago, a HP rep told me they were going to remove all Windows 9x Drivers from their website. I spent the next few months downloading their entire website. It ended up being almost 500GB after I removed foreign language and non-9x files. Lexmark did the same thing that year as well.

Not true. NVidia 6xxx and 7xxx PCI-E Video Cards are supported. I have Patches to support PCI-E PATA and SATA Cards.

Hi rloew,When I had created 4 logical 20GB FAT32 partitions on the 2TB HDD, and then right-clicked in My Computer on the 2nd FAT32 partition on the 2TB HDD, the format window of WriteUDF! came up. Although WriteUDF! displayed 20GB to be formatted to UDF, WriteUDF! actually formatted the whole 2TB HDD to UDF (no warning!). After formatting one partition with WriteUDF! the whole 2TB HDD was formatted to UDF and the 2TB HDD had only 1 drive letter, the drive letters of the other 3 logical partitions were gone. One user manual of SAI states "SAI is the only software company to guarantee that its UDF format is OSTA UDF compliant". Apparently they interpret the End of Media as the end of the Physical Disk, not the end of the Partition. This would preclude multiple Partitions as the backup headers have to be at a certain distance from the end. I assume WriteUDF uses the Drive Letter to find the Physical Drive to Format but otherwise doesn't care about the Partitions. I have a tool that can make the Hard Drive appear smaller.

There is no reason why he can't just use part of the 2TB Drive and leave the rest unused.

I have a Multi-Core SDK that can run tasks on other Cores under Windows 9X, but these tasks do not include other OSes.

Windows XP already supports multi-core. You can run your apps in a VM.

What task?

Wow! How did you format the HDD to ISO/Joliet exactly? How large was the formatted HDD? I used my RFDISK Program to create a custom MBR and set a flag in it to indicate 2K Sector Emulation. I rebooted into DOS using my DDO and copied an ISO directly to the Hard Drive except for Sector 0. After rebooting again I could access it from Windows. The formatted HD was the size of the ISO. Not particularly efficient but it worked. Using my ISO writer and Large File Emulator, I could make any size ISO. This of course requires my Terabyte Plus Patches to emulate and support the 2K Sectors. What gives me still a glimmer of hope is that about half the files extracted from the 8GB file under Win98 were Ok. If something doesn't work, then often all or most results are bad, but just 50%. Or do the 50% Ok files reflect 4GB accessible, and 4GB not accessible?Maybe 90% of the files extracted Ok from the 8GB iso seem to have been in a perhaps contiguous chunk of the iso, i.e. all files in the folders DB075 to DB119 of the extracted iso were identical to those on the DVD, while most files in the folders DB001 to DB069 of the 8GB .iso had completely different content (but identical file names and file sizes). The 4GiB limitation is on the size of the files not the entire FileSystem, but if you have created an Image (ISO) File to extract from rather than extracting from the original media, the limit applies. All of the Directories and File Info are near the beginning of the Disk. This is why all Filenames and attributes appear correct, even if the File Data is near the end. The first 4GiB of data extracted correctly, but the remainder was garbage. My intention was to extract an 8GB file into small components, not to create an 8GB file The problem is you created an 8GB ISO File. You would have had to rip the DVD-DL with my Large File Emulator active to create the Emulated ISO File, then you could extract from it. Whether UDF is read-only or read-and-write depends on the file system driver used. The MS UDF file system driver under Win98SE allows only reading from UDF files, while the SAI UDF file system driver allows reading and writing. The UDF software from SAI comes with a SAI file system switching utility, which allows to switch between the MS and the SAI file system drivers. After switching the file system driver you have to reboot. The Windows 98 Resource Kit contains some info about UDF under Win98 (pp. 1312-1319, 1213, 442, 467). True. But what I said still applies. @Dencorso: I have been experimenting with a GPT Booter but DOS and Windows would have to be modified to Enumerate GPT Partitions. I already created a MBR extension that supports 512TiB with 512 Byte Sectors, more with larger ones, that only required relatively simple Patches. It is already in my Terabyte Plus Package along with the Partitioning Tool and Formatter that supports it. 2K and XP are another story entirely. They would only use the DDO during initial loading and would revert afterwards. Implementing the MBR Extension would be less complicated.

UDF v1.02 is one of the file systems which Win98 understands and which is not tied to Microsoft. Increased knowledge about UDF under Win98 may lead to surprising results. Maybe it will eventually be possible to burn a DL-DVD from an 8GB iso on a UDF-formatted archive HDD, under Win98. Probably. I already created an ISO/Joliet Formatted Hard Disk using 2K Sector Emulation that was readable under Windows 9x. It was from a CD so it could always be reburned. I have double-clicked under Win98 on an 8GB .iso image of a DL DVD on the UDF-formatted HDD. The .iso image opened fine in UltraISO v9.3.6.2750. When I extracted under Win98 the files in the 8GB .iso image, all files extracted, but about half of them had a different content from the files on the original DL-DVD, the other half of the files were identical to the files on the original DL-DVD. The same happened when I extracted the 8GB .iso file under Win98 with WinRAR and MagicISO. IsoBuster 2.5.0.0 encountered bad sectors [non-existent in the original files] in some files when trying to extract the 8GB .iso under Win98.What is interesting in this experiment is that an 8GB file could be opened under Win98 if the 8GB file was residing on UDF v1.02 media, but something during the processing/extraction went wrong, perhaps because of some glitch in Win98. WinRAR, UltraISO and MagicISO completed the extraction of the 8GB file under Win98 without an error message, but again, about half of the stuff extracted by them was incorrect. Maybe, with a patch, or with a modification of your Large File Emulator, the 4GB file size barrier under Win98 can be broken with UDF media. Experiments under Win98 can probably be made just as well with 8GB etc iso files on UDF-formatted blu-ray BD-RE media. The internal structures used for File I/O are 32-Bits. This is why no File System can truly handle more than 4GiB Files. You may not get an error but the data will be wrong. My Large File Emulator simulates a larger File at the User API by creating multiple smaller files. This is why it works with FAT32. It won't help with actual large files on an UDF Partition. I already have created a Bootable Read/Write BD-RE that looks like a 23GB Floppy Disk, but it uses FAT32. It's a file system driver limitation, so I doubt that malware will be able to overcome this. Raw Disk I/O bypasses the File System Driver so smart malware could change even a "Read-Only" File System.

Please add the following system to the list. Motherboard: Asus M5A97 OSes: Windows 98SE + Windows 95, ME, 3.11 and XP SP3 + MSDOS 7.10, using RFDISK Multi-Boot Profile MBR Memory: 32 GiB (4x 8 GiB DDR3 DIMMs; 3069 MiB available to Win 98SE; 29692 MiB available to RAMDISKs and 64-Bit Memory SDK) CPU: AMD FX-8120 Eight Core Motherboard Ethernet and Sound Disabled (No Win 9x Drivers) USB 3 (XP Only) Video Card: NVIDIA 7200GS PCI-E (with 81.98 Driver, with shutdown problem) Sound Card: Envy24 Ethernet Card: RTL8139 2 Removable SATA Trays 1TB SATA Hard Drive currently installed Blu-Ray Writer TBPLUS Disk Package CONFIG.SYS: DEVICE=C:\HIMEMEX.SYS /S /V ; used with RAMDSK64 and 64-Bit Memory SDK. DEVICE=C:\WINDOWS\HIMEM.SYS /NUMHANDLES=64 AUTOEXEC.BAT: RAMDSK64 R: 6000000 (6GB non-XMS RAMDISK For Internet Temporaries) Remaining 64-Bit RAM reserved for 64-Bit RAM and Multi-Core SDKs. vmm32.vxd (real mode), vcache.vxd: 4.10.0.2222, vmm.vxd: 4.10.0.2226 with RAM Limitation Patch 7.1 (with /M and /P Options)

Getting Win9x/ME and 2k/XP to understand and use 4 kiB sectors, in a manufacturer agnostic way, seems to me one of the most pressing projects, ATM, since 3 TB HDDs are already out there. Getting a 3TB USB Drive to work with Windows 9x was fairly easy. Getting a 3 TB SATA Drive to work was much more complicated as it involved supporting DOS as well as upgrading the Disk Driver. A DDO is also needed if 4KB Sector emulation is required.

I'm not sure what the point of using UDF with Windows 9X is. Even if the File System can handle larger files, Windows 9x will not handle them. You need my Large File Emulator to do that. The Read-Only limitation can be bypassed by doing raw Disk I/O so it is not secure. FAT-32 can be definitely be extended to 16TiB with 4K Sectors. This can be done with or without USB.

You can make a "Live CD" for Windows 98SE but it has to be customized to the particular machine. I have already done it.

I have not researched the i295 chipset. So far, I have been able to support all modern PATA and SATA controllers, except for an AHCI-only Marvell based Highpoint Card. If it boots in AHCI Mode but can be switched to non-AHCI, I can write a DDO to support it. If it reports AHCI capability (Class 0106) but does not default to AHCI, I can support it. I can support RAID Mode (Class 0104), most SCSI Mode (0180), and Legacy, Native and IDE Mode (Class 0101) Controllers.

Problem? I don't see "IDE" anywhere in what the OP had posted, and somehow I don't think SATA "RAID" is going to help run Windows 9x. SATA RAID is not a problem unless it forces AHCI. I have alternative SATA Patches for RAID.

AHCI is NOT compatable with Windows 9x. It requires protected mode operation and Windows 9x will crash well before it could possibly load a driver. I was able to Patch the firmware on a Highpoint card to not crash, but there are no AHCI drivers for Windows 9x in any case.

It can be used with my DLLHOOK redirector. Hello rloew, I e-mailed you a few weeks ago, but maybe you did not receive my message. I was wondering whether you plan further development of your DLLHOOK software, for example to add new functions or to maintain compatibility with newer versions of KernelEx. Also, is there a listing of software possible to run on Windows 98 (SE) using DLLHOOK? Thanks! The DLLHOOK software itself is pretty stable, although I may make a customizeable VXD Version, similar to the non-customizeable FILE64.VXD. They are designed to be compatable with KernelEX 4.5.2. There are no later Versions of KernelEx. I have developed a KEXEX Project that provides stubs and non-stubbed Functions for extending KernelEx. This provided support for SumatraPDF. I have been adding Functions, Redirects and Stubs as I encounter a need. It should be able to support all of the Programs that Jumper's Kext and Import Patcher can. I don't have much of a list of programs supported by DLLHOOK as I do not routinely use KerneEx. I originally wrote DLLHOOK as an API Overlay to support my 64-Bit File Emulator. I also used it when I was experimenting with the Windows 98 Resource Problem. SumatraPDF is the only one I verified worked with DLLHOOK, KEXEX and KernelEx together. Others probably work with what I have now but I have not tested them.

22GB lost free space is a lot. I didn't know that ScanDisk under DOS can fix a 700GB FAT32 partition, but again, I have little experience with 700GB FAT32 partitions and don't use FAT32 partitions larger than 192GB. It would be interesting to hear about your experience with huge FAT32 partitions. DOS SCANDISK has no problems until you reach approx 1.28 TiB with a normally formatted Partition, and even then it is only a cosmetic problem up to 2TiB. I routinely use a 909GB Partition.