The Os 3.1.4 Thread

[my_pc_is_amiga]

I downloaded the AIFF and WAV datatypes on aminet and tried them for 3.1.4.  I then tried to play an AIFF from a CD but multiview says format not recognized.  Are the
http://aminet.net/package/util/dtype/AIFF_dtc code need to be updated for 3.1.4 to work?

[my_pc_is_amiga]

Thanks a lot for the update!   This issue with Multiview does not look like got addressed in 3.1.4.1:

https://forum.amiga.org/index.php?topic=73908.0

[my_pc_is_amiga]

Cross-posting a copy command memory leak issue from here:

http://forum.hyperion-entertainment.com/viewtopic.php?f=15&t=4321

[my_pc_is_amiga]

For the multiview issue, this one, and any other minor issue it doesn't sound like there is any plan for a 3.1.4.2...instead next release is a 3.2?

Cross-posting a copy command memory leak issue from here:

http://forum.hyperion-entertainment.com/viewtopic.php?f=15&t=4321

I afraid it is too late now.

[my_pc_is_amiga]

Not to re-hash again and again but I haven't heard anybody reproducing this.   Is this reproducible for anybody else?  It is definitely a very minor thing but just wanted to check...

Thanks a lot for the update!   This issue with Multiview does not look like got addressed in 3.1.4.1:

https://forum.amiga.org/index.php?topic=73908.0

[my_pc_is_amiga]

Sure...

If I open multiview with Execute (amiga-E) from workbench and load a text file from a requester, the text file loads properly.  I then use Workbench to go to another file and drag that icon into the multiview window, multiview will not respond to open up file and I get a error message in title bar saying icon cannot be dragged into this window. 

However, if I again load a text file via the "Open" menu item in multiview, I can load a new text file.  And then if I drag an icon into this window, it works!

If you want to get response i would recommend to at least describe the problem. i do not browse links for your convenience.

[my_pc_is_amiga]

Thanks for confirming!

Sure...

No worries. The problem has been found and fixed in the meantime. Along with the problem of "copy" you reported.

[my_pc_is_amiga]

I was trying the 68k version of the WarpBMP datatype (https://www.warpdt.co.uk/) to load a BMP picture into multiview using the 46.13 picture.datatype.  This is using Amiga native graphics (A4000T) and no graphic card installed.   

I am seeing the picture not loading correctly.  Top of screen is getting rendered incorrectly and then the whole system crashes with guru 8100 0005 after trying to quit multiview or right click for menus.

Attached is a photo of the screen after loading.

[my_pc_is_amiga]

No, I'm somebody different.   Has anybody reproduced the strange loading of pictures (e.g. BMP pictures) that causes a guru.  I'm always paranoid that I'm hitting some hardware issue with my A4000T instead of software when it comes to these memory corruptions -- feel much better if it just software since that always can get fixed .

I'm also finding that if I load a picture in multiview in full screen mode and if the picture size is small, a small screen is opened.  Because of that, there isn't enough screen real estate for the menu bar to fully show and the ASL requester cannot open properly.

I think heard that the older AIFF/WAV datatypes (that are available on Aminet) need some updating to get them to work again with the 3.1.4.   I haven't been able to get those old ones to work anymore.

Lastly, a wish that I don't think has even made it into OS4.x--to have copy and search support for amigaguide in multiivew.

@my_pc_is_amiga

Hi,

Are you also the same person posting as "Castellen" in other Amiga forums?

[my_pc_is_amiga]

I copied the picture.datatype from OS 3.9 and OS3.9bb2 versions to my 3.1.4 installation and still see same issue in the 3.1.4 environment.  I also tried bmpdt.lha on aminet and see same issue. Adpro that doesn’t use data types is okay with same BMP picture. 

Then I loaded the OS3.9 env. from an Emergency Disk that booted the CD-ROM.  I loaded up the warpbmp datatype and loaded the *bmp into multiview and no issue (no crashing or picture corruption).  Also, in the 3.9 env. multiview is giving full access to menu bar for small images -- in 3.1.4 multiview is making small screen size as reported previously.

I was trying the 68k version of the WarpBMP datatype (https://www.warpdt.co.uk/) to load a BMP picture into multiview using the 46.13 picture.datatype.  This is using Amiga native graphics (A4000T) and no graphic card installed.   

could you please test this with the Picture.datatype from 3.9 ? I also had some issues with warp-Datatypes and the new Picture.library. I allready reported this to Oliver Roberts.

It seems the warp.datatypes are the "Problem"

[my_pc_is_amiga]

I've been trying to get CrossDOSFileSystem to work with Poseidon USB Stack and have read through the FAQ, etc. but no luck.  It gets mounted but DOS says "Not a DOS disk".  Fat95 mounts but I rather use CrossDOSFileSystem.  Does anybody have a Poseidon config. that works with thumb drives?   Also, in the FAQ, it mentions, mount flags like Fat32, "DirectSCSI" -- if we were to use these, do we need to use it like this in a mountfile:

Control  = "Fat32=1, DirectSCSI=1"

[my_pc_is_amiga]

Don't know if this is related to the previous memory leak with shell "copy" command  -- but in doing a copy in workbench (drag-and-drop) from my hard drive to RAM:, I was doing a large copy.  It was enough that filled up my RAM disk.  I got the message that my RAM disk is full but after acknowledging the requester and stopping the copy, my ram was not freed properly.  My fast ram in workbench title bar showed "3,782,782,128 other memory" (~3.5GB!).   I only have 272MB of fast memory.   And doing an avail, I saw negative numbers being reported for "available" 

[my_pc_is_amiga]

I was trying to reproduce as well and haven't seen it for a 2nd time.    I tried both ways of saying "yes" and "no" but haven't reproduced.  Unfortunately, I don't have any more details of what led up to it except I'm attaching some photos of when it happened the first time.

Sorry, I cannot reproduce this here. I need better instructions for reproduction. If the RAM disk becomes full, you get a requester whether the incomplete object should be removed. If I say "no", the RAM is still full, but I see a small amount of RAM left. If I say "yes", the RAM is released.

[my_pc_is_amiga]

Is this a "superfloppy" with no partition information on it, or a partitioned disk? Thumbdrives that are pre-formatted for the PC are the latter, thus use the instructions in the FAQ. Also note the name of the drive, it should end with a 'C' or a '0' to indicate the partition number, and the right DOS type as indicated in the FAQ.

Let me check this some more...
[Edit]  Got it to work using DosType 0x4D534800 for a partition table drive -- user mistake

No, the FAQ does certainly not mention a mount flag like Fat32. Fat32 support is built into CrossDos, this is what it says. "DirectSCSI" *is* a mount flag, but you only need that for broken devices that do not support reads beyond the 4GB barrier. I am not aware that the usbscsi.device is broken, but I could be wrong. So, nothing of the above. Mount flags are just used as indicated in the FAQ:

When I look at: http://us4.aminet.net/aminet/docs/help/AmigaOS_3.1.4-FAQ.txt -- Line 652

'Note: CrossDOS supports long file names, the mount flags "EnableNSD", "DirectSCSI", Fat32, Fat16, Fat12 and Fat8.'

So "Fat32, Fat16, Fat12 and Fat8" text after the "mount flag" wording is what confused me but thanks for the clarification.

[my_pc_is_amiga]

I loaded up the 3.1.4.1 env. but using 3.9 Multiview 45.9.  No issues using the BMP datatype with the older multiview 45.9.  It seems like newer multiview 45.22 is having some issue.   I am keeping 3.1.4 picture.datatype 46.13 loaded.

I copied the picture.datatype from OS 3.9 and OS3.9bb2 versions to my 3.1.4 installation and still see same issue in the 3.1.4 environment.  I also tried bmpdt.lha on aminet and see same issue. Adpro that doesn’t use data types is okay with same BMP picture.