ExFat filesystem for Win 9x/ME
#1
Posted 08 March 2010 - 01:18 PM
4gb it's a barrier for some large files.
Can someone make this?
#2
Posted 08 March 2010 - 02:52 PM
#3
Posted 08 March 2010 - 03:18 PM
rloew, on 08 March 2010 - 02:52 PM, said:
The System APIs do not support >4GB, in particular SetFilePointer.
I know. I don't want install ExFat. There is no problem with this. It's time to fix Win98Dos and Win98 and make support for use ExFat. Here lies the rub. Blue Ray movies - 6,7,8GB. You know what I mean...
This post has been edited by Win7Box: 08 March 2010 - 05:25 PM
#4
Posted 08 March 2010 - 05:18 PM
Win7Box, on 08 March 2010 - 03:18 PM, said:
rloew, on 08 March 2010 - 02:52 PM, said:
The System APIs do not support >4GB, in particular SetFilePointer.
I know. I don't want install ExFat. There is no problem with this. It's time to fix Win98Dos and Win98 and make support for use ExFat. Here lies the rub. Blue Ray movies - 6,7,8GB. You know what I mean...
Let me translate what RLoew said: [short version] It's *impossible*!
[long version] It's *impossible* without a *major* rewrite of the whole OS. And, in case one ever did it, after a rewrite of such magnitude it wouldn't actually even *be* Win 9x anymore.
Win7Box, on 08 March 2010 - 03:18 PM, said:
Yes. The sole thing you asked was for someone to create an installable ExFat driver.
This is impossible. Then, in your next post you denied this, and instead escalated to a full system rewrite. This, while possible, is improbable and, if done, would result in a totally different OS... That said, I don't see how do you intend to continue this thread...
#5
Posted 08 March 2010 - 05:25 PM
dencorso, on 08 March 2010 - 05:18 PM, said:
[long version] It's *impossible* without a *major* rewrite of the whole OS. And, in case one ever did it, after a rewrite of such magnitude it wouldn't actually even *be* Win 9x anymore.
it's a "truth" like with esdi_506.pdr 4.10.2225 that it can not be...
#6
Posted 08 March 2010 - 05:41 PM
Win7Box, on 08 March 2010 - 05:25 PM, said:
No, it's not. And RLoew, who answered you before myself, did solve the 48-bit LBA problem before LLXX. Then he solved the RAM Limitation problem. He's one of those rare people who, single-handedly, contributed to break some of the worst barriers of Win 9x/ME. If it were feasible, belive me, he'd been working on it already.
#7
Posted 08 March 2010 - 05:46 PM
#8
Posted 08 March 2010 - 06:37 PM
Win7Box, on 08 March 2010 - 01:18 PM, said:
Did you try to manage such large files on NTFS using freeware "Paragon NTFS for Win98" driver? If yes, you should already know the answer. If not, do try and let us know the results.
The answer for now is:
There is possibility to create ExFAT driver for Win9x (and even for DOS), but it will not be fully functional.
#9
Posted 08 March 2010 - 11:48 PM
dencorso, on 08 March 2010 - 05:18 PM, said:
[long version] It's *impossible* without a *major* rewrite of the whole OS. And, in case one ever did it, after a rewrite of such magnitude it wouldn't actually even *be* Win 9x anymore.
It would not be a rewrite of the "whole" OS, but a significant rewrite of the FileSystem API code (KERNEL32.DLL and possibly IOS.VXD) to add >4GiB File support. Adding ExFat would be somewhat simpler but would have limited functionality, similar to NTFS on Windows 9X.
#10
Posted 09 March 2010 - 11:02 AM
#11
Posted 10 March 2010 - 06:32 PM
The problem is that Windows 9x filesystem (IFS) API is very low level, I mean you have to deal with such stuff as buffering, VCache, name cache, path cache, file locking, file searching on your own. To make things worse, the IFS API documentation is very poor and missing important details.
That said, it is possible to implement basic filesystem driver (FSD) but it will have poor performance, lack many features and will behave differently than built-in drivers.
Personally I don't see implementing >4GiB file support as being that much of an issue, because as I said the IFS API is very low level and you can talk almost directly to a driver from KERNEL32 but of course such support would be limited only to new FSDs written with such support in mind.
#12
Posted 10 March 2010 - 11:08 PM
But as dencorso said, if RLoew cannot fix it, then it's not likely to be fixed.
#13
Posted 11 March 2010 - 12:57 AM
Xeno86, on 10 March 2010 - 06:32 PM, said:
The problem is that Windows 9x filesystem (IFS) API is very low level, I mean you have to deal with such stuff as buffering, VCache, name cache, path cache, file locking, file searching on your own. To make things worse, the IFS API documentation is very poor and missing important details.
That said, it is possible to implement basic filesystem driver (FSD) but it will have poor performance, lack many features and will behave differently than built-in drivers.
Personally I don't see implementing >4GiB file support as being that much of an issue, because as I said the IFS API is very low level and you can talk almost directly to a driver from KERNEL32 but of course such support would be limited only to new FSDs written with such support in mind.
I never said the FSD (File System Driver) was simple, just simpler than the rewrite of the User API. Kernel32 itself limits SetFilePointer Calls to 32 Bits even though the specification for the Call is 64 Bits. Bypassing the limit check still results in truncation. If I recall correctly the internal file tables only support 32 bit positioning information.
#14
Posted 23 May 2010 - 02:02 PM
dencorso, on 08 March 2010 - 05:18 PM, said:
Win7Box, on 08 March 2010 - 03:18 PM, said:
rloew, on 08 March 2010 - 02:52 PM, said:
The System APIs do not support >4GB, in particular SetFilePointer.
I know. I don't want install ExFat. There is no problem with this. It's time to fix Win98Dos and Win98 and make support for use ExFat. Here lies the rub. Blue Ray movies - 6,7,8GB. You know what I mean...
Let me translate what RLoew said: [short version] It's *impossible*!
[long version] It's *impossible* without a *major* rewrite of the whole OS. And, in case one ever did it, after a rewrite of such magnitude it wouldn't actually even *be* Win 9x anymore.
Win7Box, on 08 March 2010 - 03:18 PM, said:
Yes. The sole thing you asked was for someone to create an installable ExFat driver.
This is impossible. Then, in your next post you denied this, and instead escalated to a full system rewrite. This, while possible, is improbable and, if done, would result in a totally different OS... That said, I don't see how do you intend to continue this thread...
rloew and dencorso, I think you should tell MDGx about this that making an exfat driver for win9x is not possible as rloew said it would require rewriting the win9x architecture.
not only that, exfat under win9x would have also required also a DRV or VXD driver for full exfat support, in case the DLL/SYS exfat drivers from xp/vista don't work under w9x. getting win9x to recognize and access exfat partitions is one thing; getting win9x to even read, write or format/partition exfat volumes is another.
This post has been edited by erpdude8: 23 May 2010 - 02:09 PM
#15
Posted 23 May 2010 - 11:44 PM
erpdude8, on 23 May 2010 - 02:02 PM, said:
not only that, exfat under win9x would have also required also a DRV or VXD driver for full exfat support, in case the DLL/SYS exfat drivers from xp/vista don't work under w9x. getting win9x to recognize and access exfat partitions is one thing; getting win9x to even read, write or format/partition exfat volumes is another.
Creating an ExFat driver is doable although a rather substantial task. It is when you go beyond the API limits, such as files larger than 4GB, that things get really hard. Tracking down all of the code that uses File Position information and/or the internal File Tables, and Patching them is a lot of work and requiring skills few people have. This is also why the Windows Resource issue is so hard to solve.
#16
Posted 11 June 2010 - 10:27 AM
Quote
I felt that I should add something here - Although it's possible to modify/replace/add APIs to system files... changing certain system APIs are only grounds for LOTS of trouble.
Programs that don't expect Windows 9x to do certain things may break when Windows 9x gives them a different result/or if certain "missing" system calls are now present. Look at what happened when Xeno and some other developers had initially attempted to add unicode support to Windows 98 - certain programs that don't expect Windows 98 to support unicode broke (My Chinese IME was one of them - and still is).
This post has been edited by sp193: 11 June 2010 - 10:27 AM
#17
Posted 12 October 2010 - 05:05 AM
however, there is a possible DOS driver that may read exfat formatted volumes.
check it out here:
http://www.bttr-soft...try.php?id=7861
#18
Posted 14 October 2010 - 03:03 AM
erpdude8, on 12 October 2010 - 05:05 AM, said:
however, there is a possible DOS driver that may read exfat formatted volumes.
check it out here:
http://www.bttr-soft...try.php?id=7861
Looks like we still have hopes, maybe 1 day exFAT will be available to 9x OSes. [native driver... any1?]
I've added the links here:
http://www.mdgx.com/drv.htm#LKU
and here:
http://www.mdgx.com/secrets.htm#NEW
HTH
- ← Shutdown problems with Kernelex 4.5 beta 2
- Windows 9x Member Projects
- Asus Eee PC and Windows 9x. →



Help
Back to top










