@Swoop

In WBStartup. If you put it in Utilities/Commodities it will not be run on startup and will therefore not do anything unless you run it manually.

@Swoop

I've seen people put it in their startup but I just dropped it in utilities and use it as needed.

Sorry I know this is a dumb question, but there is a new mixer in the contrib/AHI drawer on the OS4Final CD.

I have done a search on AW, and used 'find' on my A1, but I can't for the life of me remember where it goes.

The read me say's it is now a commodity so do I put it in utilities/comodities?
Or, do I put it in WBStartup?

Very sorry for the dumb questions.

@R-TEAM

My scsi driver has never been intended for anything else than allowing copying old stuff to ATA/SATA drives, and maybe using old scanners etc.

Now, there may be other drivers from other people in the future... Maybe an evolution of igniatios's cybppc.device ?

Regards,
--
St?phane

@lazi

it8212 is an IDE raid controller.
LSI53C8xx is a SCSI Raid controller I think.

@BobW

Quote:

Could you tell me what is the purpose of the above two kick module?

SCSI?

Bye!

@lazi

Quote:
Do you have SFS partitions? If yes you could remove it's global cache, diskcache.library.kmod, from your kicklayout to get about 20 MB more free memory (or less free memory if you have a lot of SFS partitions, without diskcache.library each one will use it's own, partition local caches instead), but much slower disk speed.

If you don't use SFS removing diskcache.library.kmod doesn't make much difference, you'd only get 15 KB more free RAM, or about 150 KB if you remove SmartFileSystem as well.

@srupprecht

memf_public is not the way.

He has to wait for a new sdk with allocvectags.

Plus he does not need getphysicaladdress, the prd's returned by getdmalist are all he needs to set his dma hardware. If his hardware does not support scatter/gather then he has to allocate his buffer using the contiguous tag of allocvectags.

If he wants to cache flush the buffer, he needs a 32 byte aligned buffer at both ends to avoid side effects of ppc cache flushes.


Regards,
--
St?phane

@lazi

How about:

;MODULE Kickstart/it8212ide.device.kmod
;MODULE Kickstart/lsi53c8xx.device.kmod
;MODULE Kickstart/3dfxVoodoo.chip

Right now with IBrowse open, The dock, CPUTemp and CPUClock I have 200 Megs free.

Edit: If I close Ibrowse I have 209 Megs free.

@Spirantho

IIRC it must be MEMF_SHARED | MEMF_HWALIGNED but I could be wrong because I never had the honour to write a DMAable driver. For GetPhysicalAddress() and friends you need to switch to Supervisor() mode, first.

@lazi

In my AmigaOS 4 Install, I removed in Devs:DOSDrivers/ all the unnecesary drivers and left only PIPE, and in Devs:DataTypes/ I removed the CDXL datatype, which I am not going to use anytime soon. In my S:Startup-Sequence I commented out the PRINTERS: assign, since I don't have a printer and will bring it back when installing one.

Hi!

I am surprised how much memory is used after booting OS4 final on my micro A1.
There is certainly some commodities in the wbstartup, so it should be normal, but 182 megs free from the installed 256 is surprised me compared to my classic Amiga experiences.

You can gain 3 more free megs if you disable some of the kickstart modules in sys:kickstart/kicklayout.

Just put a ; before each of the following lines:

MODULE Kickstart/a1floppy.device.kmod
MODULE Kickstart/sii0680ide.device.kmod
MODULE Kickstart/sii3112ide.device.kmod
MODULE Kickstart/sii3114ide.device.kmod
MODULE Kickstart/sii3512ide.device.kmod

AFAIK the sii#? modules are for sata ide controllers, and a1floppy.device is for on-board floppy controller which is not included in the micro A1.

Please reply to this topic if you have another useful hints to optimizing OS4 install.

Bye!

@sicky

While I agree with your sentiments, the fact that 4.0 is final is because it is seen to be "enough" for a release, and as it is the last release (apart from actually getting a CD) of 4.0, it is considered final. Of course, no software is ever finished, but a release comes about when it reaches a standard that is considered "fit for the use of". That, is I think, where 4.0 is now.

Of course there will be updates, things may get fixed, or improved, and those updates will form part of the 4.1 release.

Simon

@Valiant

From the UBoot main menu choose Boot sequence
then Amiga Multiboot Options
be shure there are no CD in Boot Device 1, 2, 3

Hope this help.


Regards,
Paolo

@Lio

I only played Dynamite once or twice, but I'm a fan of Bomberman games.

PAYBACK
-works under certain conditions, but doesn't feel much stable. No sound, some menu options freeze the whole machine, but it's possible to play.

WARPSNES
-used to crash, but I guess it was because it expected to find the amigainput libs. Copied those and it runs fine and with USB joystick support apparently unscathed!

TZER0
-does not work...

NAPALM
-got much further than I'd ever did (the actual game pointer showed up), but then it's black screen all the way.

@pvanni

Quote:

Bootlist? I'm sorry, I don't understand.

@BrandonLee

Dynamite does not work, got a GR when connecting to the servers list

very sad because it is one of the best multiplayer game made for Amiga.

Good news first:

MYST
-works very well. I always had some problems,mainly gfx glithces, but now it runs as it should. I still don't know what I'm supposed to do, but that's not exactly OS4's fault... ;)

NIGHTLONG
-installation script on the 1.1 CDs seems faulty.Installing from the original CDs works.Copy the PPC files to that directory and the game runs, but...the gfx have the heatwave effect. I had this before and the solution was quite simple, but I can't recall. I'm pretty sure it will work, though


I'll try WipeOut2097, Napalm (the usual suspect...) and tZer0 next...

@Antique

As rigo says go for the ISO on CD-R first but if that fails to boot and your sure the connents of the CD are fine then try the following.

Boot your OS4Upd4 from HD
Create a new partition on Your HD
Insert Disk and Install to the empty partition.
Open media toolbox
Update SLB if required
Change your boot partition to the new partition.

Alternativly

Boot your OS4upd4, backup or lha your sys: partition to another partition.
Install OS4final from CD to a new partition
Update SLB if required
soft reboot with no startup-sequence
delete everything from sys:
copy every thing over from the new partition you installed it to
then cold reboot.

You could try putting a ; infront of the usbkickstart modules in the kicklayoutfile if you are having trouble booting. It might be wise to do this before you reboot.
I know the SE had USB problems but as i never owned one i cant say for sure or not if this will help if you encounter problems.

@Rigo

I had indeed a problem booting for OS4_Final from a CDRW. So I install OS4Upd4 on an Empty partition (HD1:, backup by current OS4Upd4 Install (on HD4:) and format that partition.
I then rebooted on that new OS4_Upd4 Install and run the setup for OS4_Final from the CDRW to the newly formatted HD0: and now everything works fine...

Jerry