Welcome, Guest. Please login or register.

Author Topic: Hyperion announces OS 3.1 update  (Read 31424 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline NorthWay

  • Full Member
  • ***
  • Join Date: Jun 2003
  • Posts: 209
    • Show all replies
Re: Hyperion announces OS 3.1 update
« on: November 13, 2017, 09:26:45 PM »
a) 3.1.4 will just confuse the matter. Call it 3.14
b) Make DST work
 

Offline NorthWay

  • Full Member
  • ***
  • Join Date: Jun 2003
  • Posts: 209
    • Show all replies
Re: Hyperion announces OS 3.1 update
« Reply #1 on: November 15, 2017, 08:28:26 AM »
BTW, I'm pretty sure I saw Joanne Dow post in a Slashdot thread about Amigas just a few weeks ago.
 

Offline NorthWay

  • Full Member
  • ***
  • Join Date: Jun 2003
  • Posts: 209
    • Show all replies
Re: Hyperion announces OS 3.1 update
« Reply #2 on: November 16, 2017, 08:20:30 AM »
(New filesystems)
Quote from: Thomas Richter;833207
Yes. Actually, we have currently three.

Have you pondered anything about how the Amiga filesystems perform with non-seektime storage like SSD/flash? Has some of the old tech choices become better or worse? Any minor tunings that can align better to this?
 

Offline NorthWay

  • Full Member
  • ***
  • Join Date: Jun 2003
  • Posts: 209
    • Show all replies
Re: Hyperion announces OS 3.1 update
« Reply #3 on: November 19, 2017, 07:25:52 PM »
Since we're fishing around 3.x - was there a changelog for serial.device 43.1(?)?
 

Offline NorthWay

  • Full Member
  • ***
  • Join Date: Jun 2003
  • Posts: 209
    • Show all replies
Re: Hyperion announces OS 3.1 update
« Reply #4 on: November 20, 2017, 12:06:22 PM »
Quote from: Thomas Richter;833358
Other than that, nothing serious changed.

Thanks. I guess I will have to ReSource it to find out if the ancient A6 related bug has been fixed.
 

Offline NorthWay

  • Full Member
  • ***
  • Join Date: Jun 2003
  • Posts: 209
    • Show all replies
Re: Hyperion announces OS 3.1 update
« Reply #5 on: November 20, 2017, 01:58:30 PM »
Quote from: Thomas Richter;833369
Hopefully. Sorry if I sound stupid,but what is the A6 related bug?

Not stupid at all. There was an ancient long-lived bug where (IIRC) A6 was treated as if it was pointing to the device base while it was actually some struct on the stack.

I have the original bug report at home somewhere. Oh yes, reported by the guy who made this http://aminet.net/package/comm/misc/ArtSer37_6
 

Offline NorthWay

  • Full Member
  • ***
  • Join Date: Jun 2003
  • Posts: 209
    • Show all replies
Re: Hyperion announces OS 3.1 update
« Reply #6 on: November 21, 2017, 01:11:52 AM »
I found the original that should be in the bug db:

# Subject: Bugs in serial.device 37.4
# Type: bug
# Subsystem: serial.device
# Severity: b
# Release: KS=40.9,WB=40.6,Program=37.4
# Date: Fredag 23-Apr-93 02:53:23
# Refer: Nilsen,Petter (Ultima Thule Software ,phone +47-84-14250)
# Path: petter@pnilsen.adsp.sub.org
# ReferID: ETN007
# Config: a4000,68040,A=AA,D=AA,RAM=2megC/8megF,TD=1,HD=IDE,

### BRIEF BUG DESCRIPTION:

This is a posting on behalf of Arthur Hagen (*Art), author of the
artser.device which is a replacement device for serial.device.
He has discovered some bugs in serial.device which I have taken on
me to let you know of.

### BUG GENERATION PROCEDURE OR EXAMPLE:

Arthur Hagen writes:

There is a bug in serial.device 37.4 that seldom manifests, although
it should be fixed.  In the device's Close-routine, the macros
DISABLE/ENABLE are used without ExecBase in a6.  Normally, this won't
pose a problem, except that a byte in the positive part of the serial
structure will be temporarily trashed (luckily this is the MSB of the
mn_Pred of one of the internal IO-requests, and it won't be accessed
while multitasking is disabled).  But if this byte contains a positive
value (on a machine with 68012 or higher this could happen), inter-
rupts won't be reenabled at the correct time, but far later (if ever).

### IF THIS WORKS DIFFERENTLY ON OTHER VERSIONS OR HARDWARE, EXPLAIN:

Don't know.

### RELATED PROBLEMS:

Don't know.