Quote:

What I do is to CTRL+ALT+DEL after having inserted a CD. This flushes the memory, but keeps the kernel intact (more or less. it seem that some preferences are lost). After AROS has restarted, the CD is available from Wanderer. I don't know if there's a better way of doing this, but I don't think there is currently

EDIT: This, of course, doesn't work in the hosted version!

Try with :

The "-m" argument let you set the quantity of RAM.

The OS release RAM it doesn't use anymore, but it uses more RAM now than on a real Amiga.
You could also "AVAIL FLUSH" to release more memory (thus flushing libraries or fonts not used)

The issue for the "hosted" version of AROS on my linux box still persists.

Upon initial startup of aros-hosted, it shows 6MB of graphics memory free.
Every app or drawer/folder I open eats portions of this 6MB graphics memory.
On my real amiga, or my AIAB setup, I can close the apps and reclaim the memory.
On aros-hosted the memory just continues to dwindle and is never reclaimed.
So eventually I get to 0 or below graphics memory.

To Everyone.

Thanks!! What a great bunch of people. By the time I get this whole thing put together. It will probably be avalible in hosted anyway. I do know that Automount is not implimented in Wanderer. Is there a way to get access to a CD in Wanderer that has been mounted manually?

Dave

Quote:

By default AROS hosted has mounted only the Linux directory
[...]/AROS/bin/linux-i386/AROS as "System:" (EMU:)

But you can mount additional Linux directories. So that you can access those too under AROS. see DEVS:MountList. For example if under Linux you have mounted cdrom under /cdrom you could have following entry in DEVS:Mountlist to access it from AROS:



To be mounted by typing "mount CD0:" in some AROS shell.

The cdrom handler can use both trackdisk style and scsi style commands and in the case of AROS I think it defaults to trackdisk style cmds. I doubt direct scsi commands in ata.device are 100 % implemented/working.

The current CDROM handler uses SCSI commands to the device to access the CDROM. I am working on adding Linux host support for the CDROM handler right now. It's not that tough - I can use the unixio hidd rather much like the OSS AHI driver. The CDROM interface in Linux is really straightforward.

Note: the SCSI commands go to the ata.device. ATAPI is just SCSI over an IDE bus. Nearly all CDROMS are ATAPI and follow MMC specifications. Microsoft forced the adoption of this several years back. It's helpful for AROS now because one driver can handle most CD/DVDs.

Is that because of a technical problem or, just that making Aros be able to see devices attatched to Linux isn't done?

Ok, I really guess what I would like to know is. Lets say I am an actual AROS user and I wan't to get the most out of AROS that I can. What are the Pro's and Con's of running Native vs. Hosted?

P.S. If I wanted to say, start a bounty for something that would allow AROS to see things like CD-ROMs in hosted. Would that be extreamly hard to do?

Not directly, and nothing.

You can use Linux to copy the CD files to where AROS can access the files.

If you copy the extra stuff from AROS-Max to a normal AROS hosted setup, you are basically just recreating AROS-Max. All AROS-Max is is normal AROS with a couple extra thingys thrown in.

ok

Hosted can't access a CD-Rom? If I copy the files from AROS-MAX to AROS hosted, what will that do?