
- techtalk.cc
- Posts: 1404
- Joined: 2014-02-27 07:51
- Contact:
How to make a direct link to a specific post:
I think this is the link you're looking for:
REMOVED BY MODERATOR: Hyperlink. DUTCH LAW DOES NOT ALLOW HYPERLINKING TO WAREZ MATERIAL.
REMOVED BY MODERATOR: Hyperlink. DUTCH LAW DOES NOT ALLOW HYPERLINKING TO WAREZ MATERIAL.
I found USP 3.33 backed up on a CD. PROBLEMCHYLD if you speaking of the VMM.vxd in the sp3.cab, it's really a VMM32.vxd misnamed. This seems to be a common theme! I suspect that the extra bit that I found with RFMaster's old patch -- was originally done intentionally too -- by the German creator of the patch or perhaps even Microsoft. The extract bit seems to make the files "not executable" according to VxDLIB, DEVLIB and RPLCLDR. I'm assuming there's some purpose for doing so but, like I demonstrated, there could be an advantage to removing it. I'll post back and let you know what I find.
I hacked the two file together with a hex editor. I was able to extract the real VMM.vxd (4.10.2226) from the file when I did:
REMOVED BY MODERATOR: Hyperlink. DUTCH LAW DOES NOT ALLOW HYPERLINKING TO WAREZ MATERIAL.
It's unmodified, that's all I'm doing tonight. Bed now!
REMOVED BY MODERATOR: Hyperlink. DUTCH LAW DOES NOT ALLOW HYPERLINKING TO WAREZ MATERIAL.
It's unmodified, that's all I'm doing tonight. Bed now!
So what is the VMM.VXD contained in REMOVED BY MODERATOR: Hyperlink. DUTCH LAW DOES NOT ALLOW HYPERLINKING TO WAREZ MATERIAL.
Windows 98 Second Edition Q288430 update
File Version: 4.10.2226
Description: DOS386 VMM Kernel Version 4.0
Internal Version: 4.10.2225
Special Build Description: QFE
Created: Monday, March 05, 2001 10:26:06 AM
Are we working to mod that file? If not - why not?
Windows 98 Second Edition Q288430 update
File Version: 4.10.2226
Description: DOS386 VMM Kernel Version 4.0
Internal Version: 4.10.2225
Special Build Description: QFE
Created: Monday, March 05, 2001 10:26:06 AM
Are we working to mod that file? If not - why not?
- PROBLEMCHYLD
- Posts: 1001
- Joined: 2013-03-22 12:55
For some reason, adding the updated VMM.VXD 4.10.2226 to the original VMM32.VXD doesn't do anything. The new version becomes the original. I checked the hash. The new VMM.VXD varies in size than the original one.