Amiga.org

Amiga computer related discussion => Amiga Gaming => Topic started by: WeiXing3D on February 19, 2018, 08:21:20 PM

Title: Assigns in OS4.1
Post by: WeiXing3D on February 19, 2018, 08:21:20 PM

Testing my installation of RunInUAE in the X5000, and contrary to what my own previous experience advised me not to do, I ran an ADF game from a USB stick. Now everytime I run any application and game, either in ADF, WHDLoad, or general apps, the system is asking me for that USB stick.

How do I get rid or fix this?

Title: Re: Assigns in OS4.1
Post by: ribdevil1 on February 19, 2018, 09:42:04 PM

In your E-UAE drawer, search for  "  .uaerc_RunInUAE " file.

Edit it.

The filesystems lines are at the end of the file.


Virginio

Title: Re: Assigns in OS4.1
Post by: WeiXing3D on February 20, 2018, 01:31:23 AM

Quote from: ribdevil1;836320

In your E-UAE drawer, search for  "  .uaerc_RunInUAE " file.

Edit it.

The filesystems lines are at the end of the file.


Virginio

Gracias Virginio.

Judging by this:
# Filesystem settings for virtual devices
filesystem2=rw,DH0:Workbench:Sys:Emulation/RunInUAE/RunInUAE/WB31,1
filesystem2=ro,Work_:Work:Work:,-1
filesystem2=ro,RAM Disk2_:RAM Disk2:RAM Disk:,-1

It looks OK, isn't it?

Title: Re: Assigns in OS4.1
Post by: WeiXing3D on February 20, 2018, 04:34:06 AM

(https://drive.google.com/open?id=1oeg-RM_IgyE2cIZZeq7ZFdgAKpH5sNO5)

On a related issue, i'm having no luck running CD32 games in RunInUAE.

For instance, when running Banshee AGA/CD32, the opening screens look all OK, but when the actual game starts, I get a distorted background (the ocean rendition) and flashing screen. See picture in this link.

https://drive.google.com/open?id=1oeg-RM_IgyE2cIZZeq7ZFdgAKpH5sNO5

Is there any particular way to launch CD32 games in RunInUAE?

Title: Re: Assigns in OS4.1
Post by: PanterHZ on February 20, 2018, 06:57:39 AM

Don't know how stuff works in OS4.1, but a quick and easy fix with classic Amigas is the following:

When something requests to insert volume Example-D1: in any drive upon boot, the solution is to make sure it kind of finds what it's looking for by inserting this line at the beginning of S:User-Startup:

Assign Example-D1: Ram:

If this doesn't work, insert the line in Startup-Sequence instead (before C:IPrefs). After some time has passed, try disabling the line to see if something still requests Example-D1:. If this is not the case, the line can then be removed.

Title: Re: Assigns in OS4.1
Post by: ribdevil1 on February 20, 2018, 03:52:26 PM

Your disk seems o.k. try in startup-sequence or user-startup in the emulated disk.

Banshee : The whdl versions ( AGA and CD32 ) fails for me too. The same as your picture.

let me try the disks and CD32.

Virginio


Tested disk and CD32 versions : Works fine both versions, without any background error or glitches, so I think there's a bug in the slave of WHDL.

P.D.

The cd32 version ( not whdl for cd32 ) is in the eab ftp as the floppys version, both works.
Virginio

Title: Re: Assigns in OS4.1
Post by: lionstorm on February 20, 2018, 09:05:07 PM

something to do with diskimage maybe ?
either fire up mounter and see if there is anything in the list to umount or look in system/diskimagegui and see if there is an adf mounted.