LLXX Posted August 25, 2006 Author Share Posted August 25, 2006 WinFile has a lot of other internal limits...All I fixed was _llseek and nothing more, it may enable older programs to read/write 2Gb+ files correctly.Problem with _llseek still exists in 2000 and above, I believe M$ didn't look too much into fixing legacy API. The problem probably still exists in Vista.However I doubt anyone using 2000+ OSs is going to be using older application that use _llseek, so it is not much of a problem. Link to comment Share on other sites More sharing options...
Acheron Posted August 25, 2006 Share Posted August 25, 2006 (edited) WinFile has a lot of other internal limits...All I fixed was _llseek and nothing more, it may enable older programs to read/write 2Gb+ files correctly.Problem with _llseek still exists in 2000 and above, I believe M$ didn't look too much into fixing legacy API. The problem probably still exists in Vista.However I doubt anyone using 2000+ OSs is going to be using older application that use _llseek, so it is not much of a problem.Yes, don't fix anything if it ain't broken If you searched across Windows you would find more broken stuff. However if it isn't used it's not necessary to patch. Edited August 25, 2006 by hp38guser Link to comment Share on other sites More sharing options...
erpdude8 Posted August 26, 2006 Share Posted August 26, 2006 (edited) WinFile has a lot of other internal limits...All I fixed was _llseek and nothing more, it may enable older programs to read/write 2Gb+ files correctly.Problem with _llseek still exists in 2000 and above, I believe M$ didn't look too much into fixing legacy API. The problem probably still exists in Vista.However I doubt anyone using 2000+ OSs is going to be using older application that use _llseek, so it is not much of a problem.Yes, don't fix anything if it ain't broken If you searched across Windows you would find more broken stuff. However if it isn't used it's not necessary to patch.my sentiments exactly, LLXX and hp38guser.Right, I have installed the patch and it does not change anything to the winfile copy problem with 2GB + files on my machine.Everything is exactly the same. Size of 2GB + files is reported wrongly within winfile and trying to copy will throw an error message.File Manager [Winfile.exe] is a lousy tool for copying files, especially when copying files with long filenames which will truncate them. once you copy files with long filenames with winfile, you'll lose the long names for good and you will have to rename them in Explorer to get back your long filenames.the NT4 version of Winfile.exe which I use under my WinXP computer can use long filenames and dont have the 2GB copy problem. Edited August 26, 2006 by erpdude8 Link to comment Share on other sites More sharing options...
eidenk Posted August 26, 2006 Share Posted August 26, 2006 File Manager [Winfile.exe] is a lousy tool for copying files, especially when copying files with long filenames which will truncate them. once you copy files with long filenames with winfile, you'll lose the long names for good and you will have to rename them in Explorer to get back your long filenames.There are some utils for enhancing Winfile, LFN support, etc.. http://www.wincorner.com/http://www.winability.com/fmutils/It would be nice if someone could come up with a mean of proving the _llseek kernel patch useful for Win ME. Link to comment Share on other sites More sharing options...
Tijay Posted August 28, 2006 Share Posted August 28, 2006 I´ve a small question :It´s possible to patch the german version of the kernel32.dll ? I tried the versions posted here and they work very well - so far. But sometimes i get an error message about "mmtask". I can close the message window and everything goes at normal. No bluescreeen, no freezes. And the command windows are in an english/german mix B) Tijay Link to comment Share on other sites More sharing options...
winxpi Posted August 28, 2006 Share Posted August 28, 2006 (edited) You could use e.g. Resource Hacker to translate kernel32.dll or wait for new 98SE SP in german think it should include this patch too. Edited August 28, 2006 by winxpi Link to comment Share on other sites More sharing options...
winxpi Posted August 28, 2006 Share Posted August 28, 2006 (edited) 1. Patch shell32.dll to use newer SetFilePointer function which uses 64-bit signed integers - difficult, but possibly the most "correct" solution.2. Patch kernel32.dll _llseek to interpret seeking from the beginning with a negative offset as a positive offset - moderate, might break some other apps, but what program would want to move the file pointer past the start of the file?3. Change conditional jump at 7FCEB354 to a permanent jump - easiest, but no more pre-enlargement - is pre-enlargement really needed?Option 4 would have been the most difficult solution: 4. Patch shell32.dll and kernel32.dll *g*What does this mean "but no more pre-enlargement" ,sorry my english isn't so well.So how does this affect my system if there is no "pre-enlargement" ? Edited August 28, 2006 by winxpi Link to comment Share on other sites More sharing options...
LLXX Posted August 28, 2006 Author Share Posted August 28, 2006 (edited) For files over 192Kb, the default behavior is for Windows to create the destination file and then set its size to whatever the size of the source is, then copy the data. That's what I mean by pre-enlargement.I'm not too sure of the consequences of omitting pre-enlargement... a possible theory is that it might result in more fragmentation with multiple copies executing at once as the clusters are allocated as the file is being copied, while with pre-enlargement the clusters are already allocated before the copying begins....and no, I'm not going to patch any other language versions, simply because there are too many languages already, I'm surprised English hasn't become universal yet. Edited August 28, 2006 by LLXX Link to comment Share on other sites More sharing options...
erpdude8 Posted August 29, 2006 Share Posted August 29, 2006 (edited) ...and no, I'm not going to patch any other language versions, simply because there are too many languages already, I'm surprised English hasn't become universal yet.well not everybody living on this planet can't use Win98se in english but it would be nice if other people helped out in patching the kernel _llseek 2gb problem for other language editions of Win98se. I like winxpi's suggestion of translating the patched kernel file into a different language for those who use Win98se in other languages.There are some utils for enhancing Winfile, LFN support, etc.. http://www.wincorner.com/http://www.winability.com/fmutils/It would be nice if someone could come up with a mean of proving the _llseek kernel patch useful for Win ME.Wincorner's FMView & FMLFNs tools are NOT freeware, they're shareware. at least they're "no nag" shareware as MDGx mentioned FMLFNs on his 98SE2ME readme.txt file.some advantages of using Winfile than Windows Explorer, eidenk, are that Winfile loads a lot faster than Explorer and that Winfile does NOT suffer from the "deleting large number of files" bug that hangs Explorer for a while. when deleting a very large number of files & folders in Explorer and IE6 SP1 is installed under Win98/ME, Explorer hangs but when deleting a very large number of files/folders in File Manager, Winfile does not hang. also, you are allowed to change the "System" attribute of files & folders in Winfile.btw - LLXX and eidenk, can you comment on what CLASYS said about "RAM slowing down with age" here:http://www.msfn.org/board/index.php?showtopic=34960 Edited August 29, 2006 by erpdude8 Link to comment Share on other sites More sharing options...
MDGx Posted August 29, 2006 Share Posted August 29, 2006 Guys,The author of these [and other] 9x patches:http://www.mdgx.com/files/918547.TXThttp://www.msfn.org/board/?showtopic=77218http://www.msfn.org/board/?showtopic=58780created a new KERNEL32.DLL patch for Win98SE [raised version build (as it should be) to 4.10.2226] + WinME [raised version build (as it should be) to 4.90.3001] which fixes the correct API function, in order to be able to create/copy/rename/move/delete files [no matter which File Manager/Explorer/similar 16-bit or 32-bit tool is used] of 2 GB and larger in size and up to 4 GB.I have tested this new Kernel patch on my Win98 SE PC, and MAKE2GB testing tool works properly now.MAKE2GB tool did not work with previous KERNEL32.DLL 4.10.2225 patch by LLXX.More info from the author:KERNEL32.DLL 4.10.2226 &4.90.3001 allow file sizes up to 4 Gibyte in Win98SE & WinME,respectively.The bug that causes the 2 Gibyte file copy limit is *not* in _llseek. Thematter of fact is: _llseek simply calls SetFilePointer and Win9x'sSetFilePointer API does not comply with the official API definition.----------Value MeaningFILE_BEGIN The starting point is zero or the beginning of the file. If FILE_BEGIN is specified, DistanceToMove is interpreted as an *unsigned* location for the new file pointer.----------The buggy Win9x code always interprets DistanceToMove as a signedlocation.I have posted here the iexpress installers for 98SE + ME:WinME fix below here:http://www.mdgx.com/web.htm#MEUNew > 2 GB Files Kernel patch now fixes correct API function [setFilePointer]:* Unofficial Windows ME 2-4 GB Files Errors KERNEL32.DLL 4.90.3001 Fix:http://support.microsoft.com/?id=318293Direct download [329 KB, English]:http://www.mdgx.com/files/C2GBME.EXEMore info:http://www.msfn.org/board/?showtopic=81200Win98SE fix below here:http://www.mdgx.com/web.htm#9SUNew > 2 GB Files Kernel patch now fixes correct API function [setFilePointer]:* Unofficial Windows 98 SE 2-4 GB Files Errors KERNEL32.DLL 4.10.2226 Fix:http://support.microsoft.com/?id=318293Direct download [261 KB, English]:http://www.mdgx.com/files/COPY2GB.EXEMore info:http://www.msfn.org/board/?showtopic=81200These 2 patches also linked here:http://www.msfn.org/board/?showtopic=46581Hope this helps. Link to comment Share on other sites More sharing options...
erpdude8 Posted August 29, 2006 Share Posted August 29, 2006 Guys,The author of these [and other] 9x patches:http://www.mdgx.com/files/918547.TXThttp://www.msfn.org/board/?showtopic=77218http://www.msfn.org/board/?showtopic=58780created a new KERNEL32.DLL patch for Win98SE [raised version build (as it should be) to 4.10.2226] + WinME [raised version build (as it should be) to 4.90.3001] which fixes the correct API function, in order to be able to create/copy/rename/move/delete files [no matter which File Manager/Explorer/similar 16-bit or 32-bit tool is used] of 2 GB and larger in size and up to 4 GB.I have tested this new Kernel patch on my Win98 SE PC, and MAKE2GB testing tool works properly now.MAKE2GB tool did not work with previous KERNEL32.DLL 4.10.2225 patch by LLXX.More info from the author:KERNEL32.DLL 4.10.2226 &4.90.3001 allow file sizes up to 4 Gibyte in Win98SE & WinME,respectively.The bug that causes the 2 Gibyte file copy limit is *not* in _llseek. Thematter of fact is: _llseek simply calls SetFilePointer and Win9x'sSetFilePointer API does not comply with the official API definition.----------Value MeaningFILE_BEGIN The starting point is zero or the beginning of the file. If FILE_BEGIN is specified, DistanceToMove is interpreted as an *unsigned* location for the new file pointer.----------The buggy Win9x code always interprets DistanceToMove as a signedlocation.I have posted here the iexpress installers for 98SE + ME:WinME fix below here:http://www.mdgx.com/web.htm#MEUNew > 2 GB Files Kernel patch now fixes correct API function [setFilePointer]:* Unofficial Windows ME 2-4 GB Files Errors KERNEL32.DLL 4.90.3001 Fix:http://support.microsoft.com/?id=318293Direct download [329 KB, English]:http://www.mdgx.com/files/C2GBME.EXEMore info:http://www.msfn.org/board/?showtopic=81200Win98SE fix below here:http://www.mdgx.com/web.htm#9SUNew > 2 GB Files Kernel patch now fixes correct API function [setFilePointer]:* Unofficial Windows 98 SE 2-4 GB Files Errors KERNEL32.DLL 4.10.2226 Fix:http://support.microsoft.com/?id=318293Direct download [261 KB, English]:http://www.mdgx.com/files/COPY2GB.EXEMore info:http://www.msfn.org/board/?showtopic=81200These 2 patches also linked here:http://www.msfn.org/board/?showtopic=46581Hope this helps.MDGx, can the anonymous author patch the KERNEL32.DLL file for Win98 FE and update it to version 4.10.2002? Link to comment Share on other sites More sharing options...
winxpi Posted August 29, 2006 Share Posted August 29, 2006 (edited) * Unofficial Windows 98 SE 2-4 GB Files Errors KERNEL32.DLL 4.10.2226 Fix:http://support.microsoft.com/?id=318293Good to know and now there is no need to patch the other 98se kernel32.dll versions.This kernel32.dll should be used for new 98SE SP 2.xx version (if not an higher file version also comes out in future). Edited August 29, 2006 by winxpi Link to comment Share on other sites More sharing options...
eidenk Posted August 29, 2006 Share Posted August 29, 2006 some advantages of using Winfile than Windows Explorer, eidenk, are that Winfile loads a lot faster than Explorer and that Winfile does NOT suffer from the "deleting large number of files" bug that hangs Explorer for a while. when deleting a very large number of files & folders in Explorer and IE6 SP1 is installed under Win98/ME, Explorer hangs but when deleting a very large number of files/folders in File Manager, Winfile does not hang. also, you are allowed to change the "System" attribute of files & folders in Winfile.I couldn't be using that over explorer really but some people do. A computer dealer I know in town told me he can't use explorer. He doesn't "get it" and he just only uses winfile for browsing directories on XP.btw - LLXX and eidenk, can you comment on what CLASYS said about "RAM slowing down with age" here:http://www.msfn.org/board/index.php?showtopic=34960I don't know erpdude. First I am not very knowledgeable in the inner workings of RAM, second I don't "get" CLASYS's posts in general, so it's very hard to answer anything.But I think your question is this generic one :so guys, what do you think of CLASYS saying that all RAM "gets old" with age?So I'd say, possibly, because of electronic erosion, high energy cosmic ray hits, structural fatigue due to repeated cycles of variation of temperature. But I would think any stick dying for those reasons after a few years would have been near dead when new because of some defect. Maybe there are other factors that are more significant but I can't think of any right now.Hope this satisfies your query.Guys,The author of these [and other] 9x patches:http://www.mdgx.com/files/918547.TXThttp://www.msfn.org/board/?showtopic=77218http://www.msfn.org/board/?showtopic=58780created a new KERNEL32.DLL patch for Win98SE [raised version build (as it should be) to 4.10.2226] + WinME [raised version build (as it should be) to 4.90.3001] which fixes the correct API function, in order to be able to create/copy/rename/move/delete files [no matter which File Manager/Explorer/similar 16-bit or 32-bit tool is used] of 2 GB and larger in size and up to 4 GB.I have tested this new Kernel patch on my Win98 SE PC, and MAKE2GB testing tool works properly now.MAKE2GB tool did not work with previous KERNEL32.DLL 4.10.2225 patch by LLXX.More info from the author:QUOTEKERNEL32.DLL 4.10.2226 &4.90.3001 allow file sizes up to 4 Gibyte in Win98SE & WinME,respectively.The bug that causes the 2 Gibyte file copy limit is *not* in _llseek. Thematter of fact is: _llseek simply calls SetFilePointer and Win9x'sSetFilePointer API does not comply with the official API definition.----------Value MeaningFILE_BEGIN The starting point is zero or the beginning of the file.If FILE_BEGIN is specified, DistanceToMove is interpretedas an *unsigned* location for the new file pointer.----------The buggy Win9x code always interprets DistanceToMove as a signedlocation.I have posted here the iexpress installers for 98SE + ME:...What is the point of this patch on Windows ME ? Same question as for the LLXX patch. There is apparently no copy problem here for 2GB + files without patch. So why patching ? What's the benefit of it ? As it has already said by several in this thread, if it ain't broken, don't fix it.And has this 2GB limit somehow something to see, even loosely, with the FAT16 limit of 2GB ? Link to comment Share on other sites More sharing options...
LLXX Posted August 30, 2006 Author Share Posted August 30, 2006 Guys,The author of these [and other] 9x patches:http://www.mdgx.com/files/918547.TXThttp://www.msfn.org/board/?showtopic=77218http://www.msfn.org/board/?showtopic=58780created a new KERNEL32.DLL patch for Win98SE [raised version build (as it should be) to 4.10.2226] + WinME [raised version build (as it should be) to 4.90.3001] which fixes the correct API function, in order to be able to create/copy/rename/move/delete files [no matter which File Manager/Explorer/similar 16-bit or 32-bit tool is used] of 2 GB and larger in size and up to 4 GB.I have tested this new Kernel patch on my Win98 SE PC, and MAKE2GB testing tool works properly now.MAKE2GB tool did not work with previous KERNEL32.DLL 4.10.2225 patch by LLXX.WHAT? MAKE2GB worked perfectly fine with patched 4.10.2222 - either they broke SetFilePointer in 2225 or something else is at fault. I have also recieved reports of correct operation from other members here. MDGx please post system configuration and if at all possible, test on a virgin install. Link to comment Share on other sites More sharing options...
glocK_94 Posted August 30, 2006 Share Posted August 30, 2006 (edited) Thanks for the work here LLXX. On that + on the 137 Gig limit.But just a thing :I'm surprised English hasn't become universal yet.Wohw ! What makes you think people wish to abandon their native language ?Speaking english today is a good thing to be understood all over the world. It doesn't mean you want your OS to be in english....it had to come out. Anyway, here's my contribution : Unofficial Windows 98 SE 2-4 GB Files Errors KERNELL32.DLL 4.10.2226 Fix translated to frenchandLittyX's Kernell32.dll 4.10.2222 in french versionTijay -> send me an original kernell32.dll in german and I'll translate the fixed version if you want.Everyone -> Just tell me if you feel I should translate other versions (WinME? really?...). Edited March 7, 2007 by glocK_94 Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now