GoADF toho nabízí mnohem víc, takže k ničemu určitě není. V případě rychlého přístupu k adf bez nějakého dalšího nastavování je nový trackfile.device integrovaný přímo do systému výborný. Ale jak píše Kocour, ImageMount je úplně jiná liga. Trochu si říkám, že v AmigaOS 3.2 ubyla potřeba dodatečného tweakování systému, vše je to nějaké jednodušší .

No umí právě DMS třeba.

co GoADF to je už k ničemu?

Mně ta funkce mountování přijde docela zbytečná. Stejně člověk dojde k tomu, že potřebuje pracovat i s ISO/DMS/HDF takže pak stejně nainstaluje ImageMount

TF1260 stojí 300E bez CPU. Už začíná fungovat i TF1230, který bude stát 80E

To jsem sledoval živě. O tom pořadníku něco ví Solaris. Mě zaujal TF1200 v kombinaci s tou Buffee. Doufám, že se z toho něco vyvine.

k0x mě před nedávnem upozornil na tento rozhovor. Závěr je, že to jede na 70-80MHz, vyrábějí cca 50 kusů měsíčně, vlastní cpu nepotřebuješ (mají relativně dost) a stačí prý jen slušně požádat a jsi zařazen do pořadníku. Kolik lidí je ale před tebou není jasné. Asi docela dost. Kolik to stojí si už nepamatuju, ale TF byly vždy relativně levné karty.

Skoro bych asi i využil něco silnějšího, než je B1230-IV...

Kdybyste to náhodou ještě neviděli...

Jestli je to včetně licenčního klíče, který se bude dát registrovat na stránkách Hyperionu, tak je to v pořádku. Pokud ne, kupující bude mít trochu problém získat updaty, až časem vyjdou.

Tak na bazosi uz fici "digitalni distribuce".

A Walkero ukazuje na streamu jak to v praxi nainstalovat a použít.

EDIT: záznam

Na Aminetu už se objevil první doplněk do OS3.2, EjectADF.

Dodatky k FAQ:

1.5
* Do you have any tips that can help me with 3.2 using my current hardware and software combination?


i) Some hardware expansions emulate the Gayle Amiga custom chip to be able to provide storage features. The machines containing such expansions will most of the time be detected as another machine type during installation because of this. So please follow the Install process suggestion on Module installation even if it seems wrong at first sight, because if not, you may end up with a non-working storage media controller. This is particularly the case with expansions such as Apollo-Computers Vampire 500, IrixLabs Classic 520, most of the Terrible Fire product line, among many others.


4. Performance and compatibility


4.14 * I copied a full floppy/CD to RAM: and ended up with the RAM icon being permanently overwritten by the floppy's/CD's icon.

- In previous versions of AmigaOS, users were unable to easily replace the RAM: volume icon by following the same procedure applied to all other icons. Users had to look for elaborate workarounds or hacks to achieve that in this particular case. For AmigaOS 3.2 we decided to resolve this long standing issue by adding the following line to the Startup-Sequence: MakeLink RAMisk.info TO ENVARC:Sys/def_RAM.info SOFT What this line does is create a soft link that points to ENVARC:Sys/def_RAM.info as being the actual icon for the RAM. So now users can move the RAM icon around, snapshot its position and on the next reboot it will stay at the same location. However if you are not happy with this, by commenting this line, inserting a ";" symbol (without quotes) as its first character, the old behavior will be restored and your RAM icon will no longer be overwritten. But have in mind, that you will have to learn to live with the inconvenience previously mentioned, where the RAM icon will not be easily exchanged and/or have its position saved.

4.15 * Why am I experimenting graphic glitches in the Palette Preference editor and/or the Help subsystem?

-This is most likely the cause of the Indivision AGA MK3 scandoubler which has issues to adequately filter some lines under the current resolution. A solution which should involve a firmware core update, should be available from its manufacturer at: http://wiki.icomp.de/wiki/Indivision_AGA_MK3

4.16 * When I boot my Amiga, it stops at a black screen. What is going on?

-If you booted your Amiga with no drives at all or none gets detected, a black screen will be shown signaling that your system is inoperable. Just by adding any compatible disk drive (even a floppy one) and rebooting, the Amiga will resume the boot process as usual. So if you are performing some motherboard diagnostics without any drive you may prefer to keep the Help keyboard key depressed or hold both mouse buttons to access the Early Startup Control Menu (bootmenu).


12. ROM Modules



12.10 * Which files from the ROM directory should I use for my Amiga?

-The files in the ROM directory of the AmigaOS 3.2 distribution have two types of extensions: Files that have the ".bin" extensions are files whose only objective is to be burned into physical ROMs to insert and replace the ones you might have in your Amiga's motherboard. Files that have the ".rom" extension are unswapped and joined Kickstart images that should most of the time be used only for software related purposes like softkicking, ROM mapping, etc. So for example, for an Amiga 3000 computer, the two ROMs required should be burned by using the following files: kicka3000.bin kicka3000hi.bin Note that the Kickstart ROMs are model-specific, so ROMs cannot always be safely exchanged between models. They have been named accordingly in order to prevent confusions. REPLACING A ROM SHOULD ONLY BE ATTEMPTED BY PERSONS WITH SUFFICIENT EXPERIENCE AND EXPERTISE AS IT MAY LEAD TO DAMAGE OF THE MOTHERBOARD OR THE ROM CHIPS. YOU WILL ALSO REQUIRE AN ANTI-STATIC MAT OR EQUIVALENT PROTECTION. PROCEED AT YOUR OWN RISK! HYPERION SPECIFICALLY DISCLAIMS ANY LIABILITY FOR ANY DIRECT, INDIRECT OR CONSEQUENTIAL DAMAGES SUCH AS, WITHOUT LIMITATION, LOSS OF DATA, DAMAGED HARDWARE OR DAMAGED ROM CHIPS.

12.11 * Can I use the new Kickstart ROM v47 to boot older AmigaOS versions?

-To ensure backwards compatibility of these new Kickstart ROMs on previous OS operation, you should make sure the old OS's bootable system hard drive partition also contains both workbench.library and icon.library which can be easily sourced from the AmigaOS 3.2 Install3.2.adf image. They can be both located in the "Libs" directory and should be copied to the directory under the same name on the bootable drive volume of this former OS version. Please note that we cannot offer further support for this course of action and that such operation can only be performed at your own risk.

12.12 * I have problems flashing ROM modules into my Deneb hardware.

-The lastest version of the Luciferin program that allowed flashing ROM modules into the Deneb USB controller seems to be a bit buggy: It hangs when adding gadtools.library to the modules list. The workaround is to remove everything from flashRom, then manually add the new ROM for the matching Amiga model. The Luciferin software will offer a ROM module called AlgorKick, add this one too. Then flash and enjoy.


14. The Amiga CDTV, CDTV-II (CDTV-CR), A570 and CD32


14.14 * My custom CD32 ROM does not work with my CD32 accelerator. What can I do about this?

-Some Amiga CD32 accelerators have an issue with Gayle emulation not being precise enough to make their storage controller work and posing a problem on the AmigaOS 3.2 released scsi.device v47.4. If this particular version of the driver interface is used, hard drives are not recognized by the system when using such hardware expansions. You can either resort to using the v45.7 scsi.device from AmigaOS 3.1.4 to preserve large drive support, or use the old one v40.12 (from AmigaOS 3.1) but then having to put up with the 4 GB maximum drive size limitation. In the future a firmware fix may arrive for these accelerators from its designer/s, and on our side, we will try to make the scsi.device driver a bit more permissive on the Gayle chip specs in order to let some differences with real Gayle chips be tolerated.

Chválím obal na telefon, mám stejný.

(Paulu-Agnuse-Denisu mám také)