alexh wrote:It basically turned all disk images into "archives" just like ZIP under windows xp...All the features of windows explorer are available.
Desty wrote:It would be nice if there was a way of doing this from user-mode to avoid that problem; explorer on my laptop is crashing a lot in WinXP because of an ext2 filesystem driver.
Does Daemon Tools (the ISO image mounter) use a kernel driver to do it, or is there some trick?
ppera wrote:Stolen code? I don't know - at VDK stays that he self examined VNC structure, what is not interesting for us.
Kernel driver for mapping image as logical drive should be simple. If MS would have little better organized documentation I would not look for freeware sources.
ppera wrote:Unfortunatelly, it will not work as I expected at first.
After some tests I see that WinXP can not handle all GEMDos partition types. As I see, it expects sector size to be 512 bytes always, and works with clusters of many sectors (up to 64). While Atari uses practically always 2 sectors/cluster, and 'Big sectors' up to 8192 to achieve bigger clusters.
Or continue Drive Image, and add DIR copy and delete...
ijor wrote:VDK is based on FileDisk. And it is Vox Populi that FileDisk is (originally) stolen code. I noted that VDK has a different copyright than FileDisk, so technically, it might be not exactly derived from FileDisk. I don't know from the legal point of view, but morally, it smells the same thing, still indirectly based on stolen code.
Lautreamont wrote:It looks like FileDisk and VDK are released under the same license: GNU GPL. Legally, it's ok to take someone's code and release it under the same license without asking the author.
I don't believe that VDK can be blamed if FileDisk is stolen code, but the author should be warned that FileDisk is suspicious. If he already knows, he should be frowned at. The source files which don't have the author of FileDisk as the copyright holder are not tainted though.
ijor wrote:Windows does support bigger sector sizes (I think upto 4k, would need to check). But VDK probably doesn't.
I'd consider implementing a shell extension. Still not the same as actual mounting, but probably good enough for most purposes and you avoid the need of a kernel driver.
ppera wrote:ijor wrote:Windows does support bigger sector sizes (I think upto 4k, would need to check). But VDK probably doesn't.
I did not test it with VDK. It was test with hard disk - DOS partition table and GEMDos partition. And I'm not sure that we talk about same VDK - it should be only driver (virtual disk), and has not much with filesystem. And Winimage too did not recognise partition (Linux did). Sector size was 2K, btw.
ijor wrote:Yes, you will get the same issue with VDK, Winimage, FileDisk or whatever. The Windows FAT filesystem driver does support bigger sector sizes, but it requires support (for the bigger sector size) from the lower driver as well.
ppera wrote:I don't think that Winimage should depend on some lower level driver when works with image files.
Of course that lower level driver must support bigger sector sizes. - According to BPB values ...
But as I see, smaller FAT16 partitions use 512 sector sizes only. Must do some tests about sizes over 256MB, to 2GB - time...
ijor wrote:I didn't mean that they are released under a different license, but under a different copyright holder. Obviously, and I guess we agree, I can't get your code (with your copyright), and release it under my own copyright, disregarding any licensing issues.
ijor wrote:Hard to believe that VDK author is not aware about the issue, but it is of course possible. I actually suspect (or at least, it smells like this to me) that changing copyright was done on purpose to avoid this issue.
Instead of adapting/modifying FileDisk (which would have been risky for VDK because of the possible ilegal status of FileDisk), he "re-coded" the software and put his own copyright. Then, not being "legally derived" from FileDisk, but just inspired or conceptually based from it, the whole issue is avoided.
I didn't study both codes here, to actually judge and be certain if this the case or not.
In the best case, it still stinks morally. If VDK "simply could not happen without his great works" (quoted from VDK, and mentioning FileDisk author), then it could not happen without the real original author (that is never mentioned).
ijor wrote:Winimage is the lower driver in this case. Lower is in relation to the FAT driver.
But the problem is that the lower driver (Winimage in this case) doesn't parse the BPB. And the FAT driver doesn't tell Winimage about the bigger sector size (it is actually the other way around).But as I see, smaller FAT16 partitions use 512 sector sizes only. Must do some tests about sizes over 256MB, to 2GB - time...
Again, logical sector size must match the physical sector size. So the partition size is not relevant.
ppera wrote:In case of image files program should to do all self, at least I did so. Without any driver actually.
Physical sector size by hard disks is always 512. I don't know how you mean that logical must be same as physical...
ppera wrote:I did some tests - all FAT 16 partitions up to 2GB have 512 byte logical sector size.
"They don't actually need to be the same size. The FAT driver asks the lower driver about the device geometry. So as long as the lower disk driver reports a physical geometry with a sector size identical to the sector size in the BPB, then it should work."
It may be case, but because we don't have such hard disks, it is only academic issue.
ijor wrote:Once again, the system will format a partition using a sector size identical to the one in the drive geometry, disregarding the partition size.
It is not academic. You don't actually need such a hard disk, you "only" need to add a filter driver that would report the geometry you want to the FAT driver.
Users browsing this forum: No registered users and 2 guests