AmigaOS 3.2 and beyond

[jbenam]

Originally Posted by 512k

When it comes to the 3.2.1 update is there updated roms in the archive orc do you have to create your own

They're in the update archive. Already swapped and split, ready to be burned with any programmer that supports 16-bit EPROMs.

[klx300r]

still confused on Buffers and Block size settings so asking my fellow amigans:

for 128GB SSD drive in my Amiga 4000, OS3.2 roms, running OS3.2.1, CS-MKIII-128MB

what should I use for block size and buffers

[Thomas Richter]

In case of doubt, what the HDToolBox recommends. 4K is a good block size for SSDs and modern drives, and therefore the defaults. The amount of buffers is not critical, unless you use shapeshifter or any other program that seeks within large files. Something like 64 buffers should be ok, but you can still adjust the number later with AddBuffers.

[klx300r]

ok thanks Thomas

just tried partitioning SSD and when I go to save changes to drive it’s giving me ‘Error -3 on write!’

never seen this error before and it won’t let me save or make changes so I’m stuck?

[klx300r]

anyone else ever get the ‘Error -3 on write!’ when trying to save changes to drive after partitioning

[daxb]

I don't know what Error -3 means but I get an error 1001 with HDInstTools (I assume you use HDToolBox) when trying to save changes to drive and the partition is write protected.

[klx300r]

@ daxb

hmm so how would one remove a write protected partition other than deleting it?

heck I can’t even save partitions, or format or verify etc with my issue

[Thomas Richter]

Error -3 is "IOERR_NOCMD", which means that HDToolBox tried to issue a command the device did not recognize.

[klx300r]

Originally Posted by Thomas Richter

Error -3 is "IOERR_NOCMD", which means that HDToolBox tried to issue a command the device did not recognize.

HDToolBox read the configuration correctly as 120GB drive so is there a setting or something that can be done to solve this issue?

[daxb]

Originally Posted by klx300r

hmm so how would one remove a write protected partition other than deleting it?

Don't run or stop the program that is responsible for the protection. In my case it is MCP its (quick) format protection.

[vk3heg]

Originally Posted by klx300r

anyone else ever get the ‘Error -3 on write!’ when trying to save changes to drive after partitioning

HDToolbox is trying to save the drive configuration to a place that it can't write to...


Just put "ram:" in front of the drive configuration and it'll then work...

[klx300r]

Originally Posted by vk3heg

HDToolbox is trying to save the drive configuration to a place that it can't write to...

Just put "ram:" in front of the drive configuration and it'll then work...

I gave up and installed that SSD into an old netbook running Linux now with no issues but out of curiosity and in case that error pops up again where would one in HDToolBox be able to put 'ram:" in front of the drive configuration?

[vk3heg]

Originally Posted by klx300r

I gave up and installed that SSD into an old netbook running Linux now with no issues but out of curiosity and in case that error pops up again where would one in HDToolBox be able to put 'ram:" in front of the drive configuration?

Sorry poor wording..


Start HDToolbox, Click on "Change Drive Type", Click on "Define New", Click on "Read Configuration".


In the file name field will be "drive definitions", make it "ram:drive definitions" then click on "OK".

[AC/DC HACKER!]

Originally Posted by klx300r

I gave up and installed that SSD into an old netbook running Linux now with no issues but out of curiosity and in case that error pops up again where would one in HDToolBox be able to put 'ram:" in front of the drive configuration?

Just drag HDToolBox into RAM Disk and run HDToolBox from there. If you're a very beginner then this is the easiest method. Then HDToolBox will save the config file to RAM: which isn't a big deal to keep anyway...in 95% of cases.

[klx300r]

ok thanks guys I learned something new and if I see that error again I’ll give this ram thingy a try

[vxm]

Hello
Can muFS (see http://mufs.sourceforge.net/about.php) be used with the latest OS version?
If not, could a patch be done?
It seems that was done for OS 3.5.
Thanks

[ma693541]

Instead of using the standard Topaz 8 font, I have changed it to another font. Can you discover the bug on this Norwegian AmigaOS3.2.1 WinUAE emulated Workbench?

[boemann]

Originally Posted by ma693541

Instead of using the standard Topaz 8 font, I have changed it to another font. Can you discover the bug on this Norwegian AmigaOS3.2.1 WinUAE emulated Workbench?

No, and truthfully if you want to report a bug, please don't ask us to spend time finding it ourselves. We have seriously enough work to do already.

[fgh]

Originally Posted by ma693541

Instead of using the standard Topaz 8 font, I have changed it to another font. Can you discover the bug on this Norwegian AmigaOS3.2.1 WinUAE emulated Workbench?

I suppose you’re referring to the mix of languages.
I’ll put it in the bug tracker.

Frode

[ma693541]

Originally Posted by boemann

No, and truthfully if you want to report a bug, please don't ask us to spend time finding it ourselves. We have seriously enough work to do already.

Well. The Version numbers are for both AmigaOS3.2.1 and Kickstart 3.2.1 in the "About" Window at top left, but look at the title line, the blue one at the top. It Says 3.2 Rom, shouldn't that title line instead show 3.2.1 Rom?