Welcome, Guest. Please login or register.

Author Topic: The Os 3.1.4 Thread  (Read 240298 times)

Description:

0 Members and 6 Guests are viewing this topic.

Offline Rotzloeffel

Re: The Os 3.1.4 Thread
« Reply #404 from previous page: May 22, 2019, 07:47:03 AM »
Funny you should reply... I got my 2060 from you :)

:) haha.... OK :) Never sell things, you not have twice :)

did you set the Jumper which copies the ROM into the FastRAM? Maybe there is a Problem? I did not set this Jumper!

I use MUFastROM instead....
Save Planet Earth! It is the only one in the galaxy with fresh and cold beer :laughing:
 

Offline kirk_m

Re: The Os 3.1.4 Thread
« Reply #405 on: May 22, 2019, 04:56:51 PM »
It all works  now.  Very strange.  I messed with it a little more,   unplugging and plugging cables from the SCSI2SD itself, as well as reinstalling the ROM, and, then it booted from the SCSI2SD.  Maybe a bad connection.
-/- A500 & ACA500 & ACA1233n -/- A500 Tower & VAMPiRE II 500+ -/- A2000 & BLiZZARD 2060 -/- A3000 & CYBERSTORM MKII 040 -/- A1200 & BLiZZARD 1230 MK IV -/- A1200 & BLiZZARD 1260 -/- A4000 & 3640 -/-
 

Offline paul1981

Re: The Os 3.1.4 Thread
« Reply #406 on: May 22, 2019, 08:40:33 PM »
It all works  now.  Very strange.  I messed with it a little more,   unplugging and plugging cables from the SCSI2SD itself, as well as reinstalling the ROM, and, then it booted from the SCSI2SD.  Maybe a bad connection.

Or a glitch in the matrix  8)
 

Offline Jope

Re: The Os 3.1.4 Thread
« Reply #407 on: June 04, 2019, 08:27:20 AM »
Thomas, I have a few requests about hdtoolbox..

- Please allow it to be used on CF cards that report themselves as removable
- Please make the minimum width of a partition's gadget two or maybe even five pixels in the partitioning screen - if you have for example a 500MB boot and a 60GB work, it is very difficult (or impossible?) to select the boot partition
 

Offline Daedalus

  • Hero Member
  • *****
  • Join Date: Feb 2002
  • Posts: 893
    • Show only replies by Daedalus
    • http://www.robthenerd.com
Re: The Os 3.1.4 Thread
« Reply #408 on: June 04, 2019, 10:20:20 AM »
I'm not sure if it supports the selection methods of previous versions, but on older versions of HDToolbox you could select any partition by clicking any other partition, then using the left and right cursor keys to cycle through them. I haven't used 3.1.4 on such a large hard drive so I haven't had a need for that method in the 3.1.4 version yet.
Engineers do it with precision
--
http://www.robthenerd.com
 

guest11527

  • Guest
Re: The Os 3.1.4 Thread
« Reply #409 on: June 04, 2019, 05:40:55 PM »
- Please allow it to be used on CF cards that report themselves as removable

This is not a matter of HDToolBox. It is the matter of the host adapter to report a "random access device". This is the only device type that allows RDBs.
 

Offline thyslo

  • Newbie
  • *
  • Join Date: Feb 2019
  • Posts: 4
    • Show only replies by thyslo
Re: The Os 3.1.4 Thread
« Reply #410 on: June 06, 2019, 01:20:35 PM »
While playing around with OS 3.1.4 and WinUAE I noticed the following:

When the 68040.library from the mmulibs package is installed in libs: the OS 3.1.4 SetPatch command consumes some MBytes of memory. In my example about 5 MBytes of fast memory which were missing after SetPatch run. It seems not to be important if there really is a 68040 CPU activated or if only a 68030 is set up in WinUAE.

With 68040.library installed, SetPatch (without QUIET) reports that it is activating some 68040 related patches. Without 68040.library it does not mention 68040 related patches and the 5 MBytes are not missing.
« Last Edit: June 06, 2019, 01:33:50 PM by thyslo »
 

guest11527

  • Guest
Re: The Os 3.1.4 Thread
« Reply #411 on: June 06, 2019, 08:41:43 PM »
Yes, of course. Whether it is 5MB or some other number depends on how much main memory you have. The 5MB are for the MMU tables the 68040 requires. The "CPU Checkinstall" in the startup-sequence should actually detect the case when the 68040.library is not loaded.

Less memory goes away for the 68030, though. It's MMU has a feature called "early termination page descriptors" that can safe quite a bit of memory by avoiding duplicated table descriptors. Unfortunately, Motorola stopped supporting them with the 68040 on.
 

Offline thyslo

  • Newbie
  • *
  • Join Date: Feb 2019
  • Posts: 4
    • Show only replies by thyslo
Re: The Os 3.1.4 Thread
« Reply #412 on: June 07, 2019, 07:33:46 AM »
Ah thanks, now it makes sense:-)
 

Offline kamelito

Re: The Os 3.1.4 Thread
« Reply #413 on: June 13, 2019, 11:53:11 AM »
@Thomas Richter

> We'd love to include reaction, but we cannot.

Now it seem that you can : "Hyperion Entertainment and the AmigaOS development team would like to thank the original developers for creating ReAction and providing the opportunity to roll out ReAction on all versions of AmigaOS."

---
 Hyperion Entertainment
Full acquisition of ReAction GUI toolkit

ReAction logoBrussels, May 14, 2019

Hyperion Entertainment CVBA is pleased to announce that it has acquired full ownership of ReAction.

ReAction is the official AmigaOS GUI system since it was incorporated into AmigaOS 3.5 in 1999. With the release of AmigaOS 4 and newer it has been improved, bug-fixed and a more consistent and uniform look was created as is apparent from the various applications that make use of it. Hyperion Entertainment and the AmigaOS development team would like to thank the original developers for creating ReAction and providing the opportunity to roll out ReAction on all versions of AmigaOS.

Stay tuned for more news regarding ReAction in the near future!
 

guest11527

  • Guest
Re: The Os 3.1.4 Thread
« Reply #414 on: June 13, 2019, 09:26:44 PM »
Please don't underestimate the amount of work that has to go into this. Yes, we have reaction now. Christopher Aldi has been finally paid. It's been only 20 years... (-;

Still: Classes are in Os 4.x style at this point, need to be reviewed, to be broken down to a 3.x interface, need to be tested, and still someone has to write the prefs editors and the tools for them - as their sources were provided by H&P, and are hence are still not available. We could use the 4.x prefs editors, yet again, this means that they need to be adapted to the 3.x styles, reviewed, rewritten, tested... you get the picture. It's a long road, and we have only little man power.

So, I guess a minimal development time for this is 6-12 months, and - I personally - would believe that we should probably not delay 3.2 by that much. So maybe not right now, but certainly at some point.

Anyhow, that's in the end a management decision. Delay the process, or release sooner without reaction. A decision I really don't want to make.

 

Offline kamelito

Re: The Os 3.1.4 Thread
« Reply #415 on: June 13, 2019, 10:08:01 PM »
@Thomas Richter
Thanks  for answering. As for management décision I would suggest release early release often.
Ping me if you need QA.
 

guest21671

  • Guest
Re: The Os 3.1.4 Thread
« Reply #416 on: June 14, 2019, 05:00:06 AM »
3.2 already exists   They need to work on their numbering scheme
 

Offline kolla

Re: The Os 3.1.4 Thread
« Reply #417 on: June 14, 2019, 06:41:51 AM »
I would suggest release early release often.

Impossible!
B5D6A1D019D5D45BCC56F4782AC220D8B3E2A6CC
---
A3000/060CSPPC+CVPPC/128MB + 256MB BigRAM/Deneb USB
A4000/CS060/Mediator4000Di/Voodoo5/128MB
A1200/Blz1260/IndyAGA/192MB
A1200/Blz1260/64MB
A1200/Blz1230III/32MB
A1200/ACA1221
A600/V600v2/Subway USB
A600/Apollo630/32MB
A600/A6095
CD32/SX32/32MB/Plipbox
CD32/TF328
A500/V500v2
A500/MTec520
CDTV
MiSTer, MiST, FleaFPGAs and original Minimig
Peg1, SAM440 and Mac minis with MorphOS
 

Offline kirk_m

Re: The Os 3.1.4 Thread
« Reply #418 on: June 15, 2019, 03:23:32 PM »
I have encountered the following issue after installing 3.1.4 on a bog-standard A3000 16MHz (no expansion cards, 2mb fast, 2mb chip).

When setpatch runs after first reboot, the computer hangs with a purple screen if all caches are not disabled from early startup.  Commenting setpatch out allows the system to run if you haven't disabled the caches.  Using NODATACACHE NODATABURST NOCACHE NOBURST  in the startup sequence does not prevent the lockup -- all caches have to be disabled in the BOOT OPTIONS of early startup menu.

I have installed MMULIB to get the 68030.library for the install, same result.

I've run out of ideas now on how to get things working properly.  Any help is appreciated.
-/- A500 & ACA500 & ACA1233n -/- A500 Tower & VAMPiRE II 500+ -/- A2000 & BLiZZARD 2060 -/- A3000 & CYBERSTORM MKII 040 -/- A1200 & BLiZZARD 1230 MK IV -/- A1200 & BLiZZARD 1260 -/- A4000 & 3640 -/-
 

Offline kirk_m

Re: The Os 3.1.4 Thread
« Reply #419 on: June 16, 2019, 02:02:29 AM »
I figured it out.  The 3000 had 2mb of fast ram, all ZIPs.  They were all fast page mode, so I swapped them out for Static Column zips and now burst works, since FPM memory and burst are incompatible.
-/- A500 & ACA500 & ACA1233n -/- A500 Tower & VAMPiRE II 500+ -/- A2000 & BLiZZARD 2060 -/- A3000 & CYBERSTORM MKII 040 -/- A1200 & BLiZZARD 1230 MK IV -/- A1200 & BLiZZARD 1260 -/- A4000 & 3640 -/-