Welcome, Guest. Please login or register.
Amiga Kit Amiga Store Hollywood MAL AMIStore App Store A600 Memory

AuthorTopic: The Os 3.1.4 Thread  (Read 60655 times)

0 Members and 2 Guests are viewing this topic.

Offline TribbleSmasher

Re: The Os 3.1.4 Thread
« Reply #525 on: July 13, 2019, 01:22:55 PM »
Well, fourth result with Google, while context is given away in the first result...

Offline my_pc_is_amiga

Re: The Os 3.1.4 Thread
« Reply #526 on: July 13, 2019, 09:57:03 PM »
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
 

Offline TribbleSmasher

Re: The Os 3.1.4 Thread
« Reply #527 on: July 14, 2019, 12:40:42 AM »
If you want to get response i would recommend to at least describe the problem. i do not browse links for your convenience. ;)
 

Offline Dynamic_Computing

Re: The Os 3.1.4 Thread
« Reply #528 on: July 14, 2019, 01:35:45 AM »
I understand that this thread has devolved into a few people whining, but I have just published a video on the new patch released this week! I try to keep it basic, but informative, to cater to more people. I hope it helps some people! Keep up the fantastic work, everyone!

https://youtu.be/a2eAol231j4

Offline my_pc_is_amiga

Re: The Os 3.1.4 Thread
« Reply #529 on: July 14, 2019, 04:57:37 AM »
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. ;)
 

Offline Thomas Richter

Re: The Os 3.1.4 Thread
« Reply #530 on: July 14, 2019, 07:52:26 AM »
Sure...
No worries. The problem has been found and fixed in the meantime. Along with the problem of "copy" you reported.
 
The following users thanked this post: my_pc_is_amiga

Offline my_pc_is_amiga

Re: The Os 3.1.4 Thread
« Reply #531 on: July 14, 2019, 03:03:32 PM »
Thanks for confirming!

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

Offline wiser3

Re: The Os 3.1.4 Thread
« Reply #532 on: July 14, 2019, 04:47:18 PM »
Well, probably time to continue with another episode. This time with my "most beloved component", which is HDToolBox.

With the latest release do we still have to enter "0x1FE00" in the MaxTransfer setting box? If so, why? Please explain more about this setting and what it take for HDToolBox to figure it out itself.
 

Offline Thomas Richter

Re: The Os 3.1.4 Thread
« Reply #533 on: July 14, 2019, 09:14:27 PM »
With the latest release do we still have to enter "0x1FE00" in the MaxTransfer setting box?
Yes.

If so, why?
Another unforeseen bug in the scsi.device. The current scsi.device, which was backported from an Os 4 version, unfortunately performs a read on write-only IDE registers to determine the continuation position of a long transfer that had to be truncated, and thus continues from the wrong point on.

This issue has been found and fixed in the meantime and will be resolved with the next version of the scsi.device.

Online kolla

Re: The Os 3.1.4 Thread
« Reply #534 on: July 15, 2019, 07:05:09 AM »
So how will next version of scsi.device be "rolled out"?
Part of free update 3.1.4.1.5 loaded with LoadModule? OS 3.2 as a new product, with new floppies and kickstart chips to buy?
Questions that nobody can answer?
B5D6A1D019D5D45BCC56F4782AC220D8B3E2A6CC
 

Offline Rotzloeffel

Re: The Os 3.1.4 Thread
« Reply #535 on: July 17, 2019, 03:22:49 PM »
We could... but we don´t want to  8)
Save Planet Earth! It is the only one in the galaxy with fresh and cold beer :laughing:
 

Offline Matt_H

Re: The Os 3.1.4 Thread
« Reply #536 on: July 18, 2019, 12:55:06 AM »
Two things:

First, Thomas, thanks so much for the work you and Olaf (and others?) are doing to polish up 3.1. It’s really great to see the classic “lightweight” branch of the OS maintained again. I’ve bought versions for my 4000T and my 2000.

Second, does the 3000 version come with a SuperKickstart file compatible with the 1.4 ROMs?
 

Offline Thomas Richter

Re: The Os 3.1.4 Thread
« Reply #537 on: July 18, 2019, 10:57:45 AM »
Second, does the 3000 version come with a SuperKickstart file compatible with the 1.4 ROMs?
No, sorry, it does not. The ROM is a regular A3000 ROM. This being said, some users successfully converted it to a superkickstart file. As far as I remember, all you had to do is to attach the right superkickstart code at its end, where this code just comes from the original superkickstart file.
 

Offline Matt_H

Re: The Os 3.1.4 Thread
« Reply #538 on: July 18, 2019, 05:46:03 PM »
No, sorry, it does not. The ROM is a regular A3000 ROM. This being said, some users successfully converted it to a superkickstart file. As far as I remember, all you had to do is to attach the right superkickstart code at its end, where this code just comes from the original superkickstart file.

Ah, oh well. Is an official SuperKickstart planned for a later update?  Good to know there are potential workarounds in the meantime.

In the absence of a physical ROM replacement, can LoadModule successfully load in the 3.1.4 modules on a 1.4 system? (after SuperKickstart 3.1 has been softkicked, of course)
 

Offline hth313

Re: The Os 3.1.4 Thread
« Reply #539 on: July 18, 2019, 07:54:19 PM »
The bonus code is the part after 512K of any 2.x or 3.x superkickstart file.

During startup it is copied onto the last 4K of the actual kickstart image, the MMU is configured so that this RAM image loaded appears in the ROM location and write protects it. Then the system resets and your soft kicked image is now the “ROM”. As long as you do not fiddle with the MMU in a bad way it stays there and appears to be the ROM so ordinary resident tricks should work the same as with a real ROM.