05 March 2009, 20:35 | #1 |
Registered User
Join Date: Jan 2002
Location: Germany
Posts: 7,035
|
A few suggestions
I'd like to see these in one of the next WinUAE releases:
- a newly created ADF should appear in the drop down list next to the floppy drives. This would come next to the hard drives panel where a new HDF immediately appears in the HDD list. - option to create PC floppy images (720K / 1440K). Now that WinUAE supports these images for use with CrossDOS and the like, it should also be able to create them. - support for 64bit packets in file system emulation for use with files bigger than 4GB. Currently they are only supported by SFS2. Would be níce to see them in NTFS directories, too. A sample 68k application and an extract from the OS 4.1 autodocs are attached. |
06 March 2009, 08:52 | #2 | |||
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,574
|
Quote:
Quote:
Quote:
|
|||
06 March 2009, 09:17 | #3 | |
Registered User
Join Date: Jan 2002
Location: Germany
Posts: 7,035
|
Quote:
|
|
06 March 2009, 13:47 | #4 | |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,574
|
Quote:
Extended adf is completely unformatted because it is not logical format specific image. |
|
06 March 2009, 16:46 | #5 |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,574
|
How are >4G (or >2G if size is considered signed) files supposed to appear with regular 32-bit filesystem? (for example network filesystem, standard fs of course can't both support and not support >4G files )
Size truncated to 32-bits or are they shown as 2^32 - 1 (or 2^31 -1)? Or hidden completely? EDIT: I guess limiting to 2^31 - 1 is good enough solution (size appears to be signed) Last edited by Toni Wilen; 06 March 2009 at 18:07. |
06 March 2009, 19:47 | #6 | |||
Registered User
Join Date: Jan 2002
Location: Germany
Posts: 7,035
|
Quote:
Quote:
The same happens for a Windows share mounted with SMBFS. I vaguely remember a discusion where it was suggested that you can get a quite good approximation of the real file size if you multiply the number of blocks with the block size and then replace the lower 32 bits by fib_FileSize. But I think this was only a question, not an official recommendation. Quote:
|
|||
06 March 2009, 19:54 | #7 | |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,574
|
Quote:
I still think limiting to 2G - 1 is most logical choice. (when not using 64-bit packets) |
|
06 March 2009, 22:17 | #8 |
Registered User
Join Date: Jan 2002
Location: Germany
Posts: 7,035
|
|
07 March 2009, 16:03 | #9 |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,574
|
64-bit packets implemented in beta 15. Test please
|
08 March 2009, 11:02 | #10 |
Registered User
Join Date: Jan 2002
Location: Germany
Posts: 7,035
|
The new packages, although working correctly, return an IoErr (dp_Res2) of -1. This should be 0.
The normal Seek() function should work inside the first 2GB of the file. It should only fail when trying to seek past the 2GB limit. When using Examine() the fib_NumBlocks field should contain the correct value, even if you fake the fib_Size field. |
08 March 2009, 13:23 | #11 | |||
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,574
|
Quote:
Quote:
Quote:
|
|||
08 March 2009, 14:04 | #12 |
Registered User
Join Date: Jan 2002
Location: Germany
Posts: 7,035
|
|
08 March 2009, 15:15 | #13 |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,574
|
What if read or write is called when file position is very close to 2G border and written/read data gets over border?
(too many corner cases, should I even care? ) |
08 March 2009, 16:09 | #14 |
Registered User
Join Date: Jan 2002
Location: Germany
Posts: 7,035
|
Read and Write work normally everywhere in the file. There is no 64bit replacement for Read and Write. Read and Write don't return file position anyway.
If the new position after Read or Write is above 2G, a subsequent Seek will fail. Note that Seek succeeds if you seek past the 2GB limit, but the old position (which is returned) was below 2GB. Actually there is no corner case IMHO. If the return value of Seek is >= 2G, it fails. Otherwise it succeeds. As Seek returns the old file position, you can even check it before you execute the Seek. |
10 March 2009, 22:11 | #15 |
Global Moderator
Join Date: Sep 2008
Location: Might as well be WORK :(
Age: 57
Posts: 4,110
|
Suppose this is as good a place to add this suggestion as any, sorry thomas for hijacking your thread slightly.
When you select a disk image the file types always default to the standard Amiga Floppy disk images, this is great most of the time, but as I'm not loading in standard disk images, I need to keep selecting 'All files (*.*)' for everything I need to load up. Would it be possible to incorporate a feature into WinUAE to either remember the last selection or add a switch into the load image file screen, so the user has the option to switch it on or off. |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
A few suggestions | Eclipse | HOL suggestions and feedback | 4 | 09 March 2011 21:19 |
Suggestions | Leandro Jardim | support.WinUAE | 1 | 14 August 2010 08:14 |
Some suggestions | girv | HOL suggestions and feedback | 0 | 15 November 2006 13:52 |
Suggestions | killergorilla | request.UAE Wishlist | 7 | 09 September 2005 12:46 |
Some suggestions | Antiriad | Games images which need to be WHDified | 12 | 16 May 2004 21:01 |
|
|