English Amiga Board


Go Back   English Amiga Board > Support > support.WinUAE

 
 
Thread Tools
Old 10 January 2015, 11:18   #1
lonestar
 
Posts: n/a
No Boot AmigaOS 4.1 - No Expansion

Good morning

This is my first post in this community, as a long and heavy Amiga User im really pleased that i can use WINUAE.

I've buyed some days ago the Original Amiga OS 4.1 FE CD for Classic Amiga's and tryed to make it towork.

I've followed several guide's from this forum but i've think i've got a Major error or bug.

Problem 1:
When i'm starting Winuae with my OS 4.1 Config everything went fine i can see the Amiga DOS Screen booting the Disk. The i receive a violett Screen with the following message.

--> snip
PPC Native OS booted with UAE boot ROM active. UAE expansions
are not hardware emulated and are not PPC compatible. (UAE HD controller,
uaescsi.device, uaeserial, bsdsocket and so on..)
<-- snap

Problem 2:
I think this is my Major Problem, when i'm only starting the WINUA Programm without any config loaded or session running i can not Access the "Expansions" Tab in the left side. The Program freezes, and it's really not possible to stop the program with the Windows Task Manager.

Attached you'll find some screenshots and log-files.

Any advise?

Best regards

- André



Attached Files
File Type: txt log.txt (37.6 KB, 265 views)
File Type: txt log3.txt (76.4 KB, 216 views)

Last edited by lonestar; 10 January 2015 at 11:27.
 
Old 10 January 2015, 11:48   #2
Toni Wilen
WinUAE developer
 
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,514
1: Disable all UAE expansion options. (UAE controller harddrives, uaescsi, bsdsocket, uaenet, uaeserial and so on)

2: My guess is that your system has broken winpcap installed (or some other application that has installed it). Expansion panel checks if it exists before enabling winpcap network option. Driver problem in any case if Task Manager does not kill it.
Toni Wilen is offline  
Old 10 January 2015, 12:56   #3
lonestar
 
Posts: n/a
Hello Toni

Thanks a lot for your help.

Problem 1: still exists, i've deactivated everything that you told but i still got the violett Screen after loading the Kickstart message

Problem 2: solved, after uninstalling winpcap!

Regards

- André
 
Old 10 January 2015, 13:07   #4
Toni Wilen
WinUAE developer
 
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,514
Your logs show directory filesystem added and OS4 CD mounted with uaescsi.device. It isn't going to work.

Also you have A1200 KS ROM but A4000-like hardware. Don't mix and match hardware features.
Toni Wilen is offline  
Old 10 January 2015, 13:13   #5
fryguy
Registered User
 
Join Date: Aug 2005
Location: Skarabörg, Sweden
Age: 44
Posts: 1,020
You can use this guide http://eab.abime.net/showthread.php?t=75264
fryguy is offline  
Old 10 January 2015, 18:14   #6
Steve
I Identify as an Ewok
 
Steve's Avatar
 
Join Date: Jul 2001
Location: North Lincolnshire
Age: 45
Posts: 2,356
That guide-files.adf that you put in the zone doesn't work. I've just tried to have a look at it and it says the disk has read errors and can't be read.
Attached Thumbnails
Click image for larger version

Name:	Guide-Files_001.jpg
Views:	564
Size:	47.7 KB
ID:	42770  
Steve is offline  
Old 10 January 2015, 18:47   #7
fryguy
Registered User
 
Join Date: Aug 2005
Location: Skarabörg, Sweden
Age: 44
Posts: 1,020
Quote:
Originally Posted by Steve View Post
That guide-files.adf that you put in the zone doesn't work. I've just tried to have a look at it and it says the disk has read errors and can't be read.
Strange, just downloaded it and tried it in OS4.1. I was able to able all files from it to ram:
fryguy is offline  
Old 11 March 2015, 13:01   #8
Khylrion
Registered User
 
Join Date: Mar 2015
Location: Earth
Posts: 21
I have the same issue under your error 1 (hanging at pink screen). Followed 4 different guides to the letter (different setups - only ide, with accelerated ppc scsi, ...) Trying to fix this as well. As soon as I have a working setup I will let you know.
Khylrion is offline  
Old 27 May 2015, 23:38   #9
Reth
Registered User
 
Join Date: Feb 2015
Location: Germany
Posts: 64
Same problem here. Regardless whether I boot from AOS4 CD Image directly or using BootFloppy.adf I get stuck in Purple Screen with reboot loop (the last time I had this was in my early days as beta tester on my A4000 CSPPC).

I also get the WinUAE message described above but do not know what I still might have activated:
"PPC Native OS booted with UAE boot ROM active. UAE expansions are not hardware emulated and are not PPC compatible. (UAE HD controller, uaescsi.device, uaeserial, bsdsocket and so on..)"
Reth is offline  
Old 28 May 2015, 00:22   #10
FOL
PSPUAE DEV
 
FOL's Avatar
 
Join Date: Nov 2006
Location: Wales / UK
Age: 45
Posts: 6,007
Send a message via MSN to FOL
Quote:
Originally Posted by Reth View Post
Same problem here. Regardless whether I boot from AOS4 CD Image directly or using BootFloppy.adf I get stuck in Pink Screen with reboot loop (the last time I had this was in my early days as beta tester on my A4000 CSPPC).

I also get the WinUAE message described above but do not know what I still might have activated:
"PPC Native OS booted with UAE boot ROM active. UAE expansions are not hardware emulated and are not PPC compatible. (UAE HD controller, uaescsi.device, uaeserial, bsdsocket and so on..)"
As Toni, said remove all the stuff its moaning about.

I used to get this with incorrect setting in RTG card settings.
FOL is offline  
Old 28 May 2015, 00:36   #11
Reth
Registered User
 
Join Date: Feb 2015
Location: Germany
Posts: 64
One thing which was activated was uaescsi.device. Deactivating it did not change anything - still reboot loop after that WinUAE message. When switching back to config it was shown as activated again but with all other fields disabled, after restart it was deactivated again.

Below the config I used. If there is still something wrong - any hint is appreciated. Also appreciated if somebody could post/send me his/her config which was used to install and use AOS4.1.

config_description=UAE default configuration
config_hardware=true
config_host=true
config_version=3.0.0
config_hardware_path=
config_host_path=
win32.rom_path=./
win32.floppy_path=./
win32.hardfile_path=./
; host-specific
win32.soundcard=0
win32.soundcardname=Primärer Soundtreiber
win32.soundcardname.utf8=Primärer Soundtreiber
win32.cpu_idle=150
; common
use_gui=yes
use_debugger=false
kickstart_rom_file=C:\Users\WIR\Documents\Computer\Amiga\AmigaROMs\kick40068.A4000
kickstart_rom_file_id=D6BAE334,KS ROM v3.1 (A4000)
kickstart_ext_rom_file=
a2091_rom_file=
a4091_rom_file=
fastlane_rom_file=
oktagon2008_rom_file=
cpuboard_rom_file=
cpuboard_ext_rom_file=
flash_file=
cart_file=
rtc_file=
kickshifter=false
ks_write_enabled=false
floppy0=
floppy0type=1
floppy1=
floppy1type=1
floppy2=
floppy3=
nr_floppies=2
floppy_speed=0
floppy_volume=33
cd_speed=100
parallel_on_demand=false
serial_on_demand=false
serial_hardware_ctsrts=true
serial_direct=false
scsi=false
uaeserial=false
sana2=false
sound_output=normal
sound_channels=stereo
sound_stereo_separation=7
sound_stereo_mixing_delay=0
sound_max_buff=16384
sound_frequency=44100
sound_interpol=anti
sound_filter=emulated
sound_filter_type=enhanced
sound_volume=0
sound_volume_cd=0
sound_auto=true
sound_stereo_swap_paula=false
sound_stereo_swap_ahi=false
comp_trustbyte=direct
comp_trustword=direct
comp_trustlong=direct
comp_trustnaddr=direct
comp_nf=true
comp_constjump=true
comp_oldsegv=false
comp_flushmode=soft
compfpu=true
comp_midopt=false
comp_lowopt=false
avoid_cmov=false
cachesize=8192
joyport0=mouse
joyport0autofire=none
joyport1=kbd1
joyport1autofire=none
bsdsocket_emu=false
synchronize_clock=false
maprom=0x0
parallel_postscript_emulation=false
parallel_postscript_detection=false
ghostscript_parameters=
parallel_autoflush=5
gfx_display=0
gfx_display_rtg=0
gfx_framerate=1
gfx_width=720
gfx_height=568
gfx_top_windowed=0
gfx_left_windowed=0
gfx_width_windowed=720
gfx_height_windowed=568
gfx_width_fullscreen=800
gfx_height_fullscreen=600
gfx_refreshrate=0
gfx_autoresolution=0
gfx_autoresolution_vga=true
gfx_backbuffers=2
gfx_backbuffers_rtg=1
gfx_vsync=false
gfx_vsyncmode=normal
gfx_vsync_picasso=false
gfx_vsyncmode_picasso=normal
gfx_lores=false
gfx_resolution=hires
gfx_lores_mode=normal
gfx_flickerfixer=false
gfx_linemode=double
gfx_fullscreen_amiga=false
gfx_fullscreen_picasso=false
gfx_center_horizontal=none
gfx_center_vertical=none
gfx_colour_mode=16bit
gfx_blacker_than_black=false
gfx_api=direct3d
immediate_blits=false
waiting_blits=automatic
ntsc=false
genlock=false
chipset=aga
collision_level=playfields
chipset_compatible=A4000
ciaatod=50hz
ksmirror_e0=false
ide=a4000
fatgary=0
ramsey=15
z3_autoconfig=true
fastmem_size=0
a3000mem_size=8
mbresmem_size=128
z3mem_size=0
z3mem_start=0x10000000
bogomem_size=0
cpuboard_type=CyberStormPPC
cpuboardmem1_size=128
gfxcard_size=0
gfxcard_type=ZorroIII
gfxcard_hardware_vblank=false
gfxcard_hardware_sprite=true
chipmem_size=4
cpu_speed=max
cpu_throttle=0.0
cpu_type=68040
cpu_model=68060
fpu_model=68060
ppc_model=automatic
ppc_cpu_idle=disabled
cpu_compatible=false
cpu_24bit_addressing=false
ppc_implementation=auto
cpu_cycle_exact=false
blitter_cycle_exact=false
cycle_exact=false
fpu_strict=false
rtg_nocustom=true
rtg_modes=0x212
log_illegal_mem=false
kbd_lang=us
input.config=0
input.joymouse_speed_analog=100
input.joymouse_speed_digital=10
input.joymouse_deadzone=33
input.joystick_deadzone=33
input.analog_joystick_multiplier=15
input.analog_joystick_offset=-1
input.mouse_speed=100
input.autofire_speed=600
input.1.joystick.0.empty=true
input.1.joystick.1.empty=true
input.1.joystick.2.empty=true
input.1.joystick.3.empty=true
input.1.joystick.4.empty=true
input.1.joystick.5.empty=true
input.1.joystick.6.empty=true
input.1.joystick.7.empty=true
input.1.joystick.8.empty=true
input.1.joystick.9.empty=true
input.1.joystick.10.empty=true
input.1.joystick.11.empty=true
input.1.joystick.12.empty=true
input.1.joystick.13.empty=true
input.1.joystick.14.empty=true
input.1.joystick.15.empty=true
input.1.joystick.16.empty=true
input.1.joystick.17.empty=true
input.1.joystick.18.empty=true
input.1.joystick.19.empty=true
input.1.mouse.0.friendlyname=Windows mouse
input.1.mouse.0.name=WINMOUSE1
input.1.mouse.0.empty=true
input.1.mouse.1.friendlyname=HID-konforme Maus
input.1.mouse.1.name=\\?\HID#VID_05FE&PID_0011#6&1f02c73c&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}
input.1.mouse.1.empty=true
input.1.mouse.2.friendlyname=Synaptics PS/2 Port TouchPad
input.1.mouse.2.name=\\?\ACPI#SYN014B#4&4112574&0#{378de44c-56ef-11d1-bc8c-00a0c91405dd}
input.1.mouse.2.empty=true
input.1.mouse.3.empty=true
input.1.mouse.4.empty=true
input.1.mouse.5.empty=true
input.1.mouse.6.empty=true
input.1.mouse.7.empty=true
input.1.mouse.8.empty=true
input.1.mouse.9.empty=true
input.1.mouse.10.empty=true
input.1.mouse.11.empty=true
input.1.mouse.12.empty=true
input.1.mouse.13.empty=true
input.1.mouse.14.empty=true
input.1.mouse.15.empty=true
input.1.mouse.16.empty=true
input.1.mouse.17.empty=true
input.1.mouse.18.empty=true
input.1.mouse.19.empty=true
input.1.keyboard.0.friendlyname=HID-Tastatur
input.1.keyboard.0.name=\\?\HID#HPQ0006&Col02#3&1f5eafa&0&0001#{884b96c3-56ef-11d1-bc8c-00a0c91405dd}
input.1.keyboard.0.empty=false
input.1.keyboard.0.disabled=false
input.1.keyboard.1.friendlyname=Standard 101/102-Key or Microsoft Natural PS/2 Keyboard with HP QLB
input.1.keyboard.1.name=\\?\ACPI#PNP0303#4&4112574&0#{884b96c3-56ef-11d1-bc8c-00a0c91405dd}
input.1.keyboard.1.empty=false
input.1.keyboard.1.disabled=false
input.1.keyboard.2.friendlyname=WinUAE null keyboard
input.1.keyboard.2.name=NULLKEYBOARD
input.1.keyboard.2.empty=false
input.1.keyboard.2.disabled=false
input.1.keyboard.3.empty=true
input.1.keyboard.4.empty=true
input.1.keyboard.5.empty=true
input.1.keyboard.6.empty=true
input.1.keyboard.7.empty=true
input.1.keyboard.8.empty=true
input.1.keyboard.9.empty=true
input.1.keyboard.10.empty=true
input.1.keyboard.11.empty=true
input.1.keyboard.12.empty=true
input.1.keyboard.13.empty=true
input.1.keyboard.14.empty=true
input.1.keyboard.15.empty=true
input.1.keyboard.16.empty=true
input.1.keyboard.17.empty=true
input.1.keyboard.18.empty=true
input.1.keyboard.19.empty=true
input.1.internal.0.friendlyname=Internal events
input.1.internal.0.name=INTERNALEVENTS1
input.1.internal.0.empty=true
input.2.joystick.0.empty=true
input.2.joystick.1.empty=true
input.2.joystick.2.empty=true
input.2.joystick.3.empty=true
input.2.joystick.4.empty=true
input.2.joystick.5.empty=true
input.2.joystick.6.empty=true
input.2.joystick.7.empty=true
input.2.joystick.8.empty=true
input.2.joystick.9.empty=true
input.2.joystick.10.empty=true
input.2.joystick.11.empty=true
input.2.joystick.12.empty=true
input.2.joystick.13.empty=true
input.2.joystick.14.empty=true
input.2.joystick.15.empty=true
input.2.joystick.16.empty=true
input.2.joystick.17.empty=true
input.2.joystick.18.empty=true
input.2.joystick.19.empty=true
input.2.mouse.0.friendlyname=Windows mouse
input.2.mouse.0.name=WINMOUSE1
input.2.mouse.0.empty=true
input.2.mouse.1.friendlyname=HID-konforme Maus
input.2.mouse.1.name=\\?\HID#VID_05FE&PID_0011#6&1f02c73c&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}
input.2.mouse.1.empty=true
input.2.mouse.2.friendlyname=Synaptics PS/2 Port TouchPad
input.2.mouse.2.name=\\?\ACPI#SYN014B#4&4112574&0#{378de44c-56ef-11d1-bc8c-00a0c91405dd}
input.2.mouse.2.empty=true
input.2.mouse.3.empty=true
input.2.mouse.4.empty=true
input.2.mouse.5.empty=true
input.2.mouse.6.empty=true
input.2.mouse.7.empty=true
input.2.mouse.8.empty=true
input.2.mouse.9.empty=true
input.2.mouse.10.empty=true
input.2.mouse.11.empty=true
input.2.mouse.12.empty=true
input.2.mouse.13.empty=true
input.2.mouse.14.empty=true
input.2.mouse.15.empty=true
input.2.mouse.16.empty=true
input.2.mouse.17.empty=true
input.2.mouse.18.empty=true
input.2.mouse.19.empty=true
input.2.keyboard.0.friendlyname=HID-Tastatur
input.2.keyboard.0.name=\\?\HID#HPQ0006&Col02#3&1f5eafa&0&0001#{884b96c3-56ef-11d1-bc8c-00a0c91405dd}
input.2.keyboard.0.empty=false
input.2.keyboard.0.disabled=false
input.2.keyboard.1.friendlyname=Standard 101/102-Key or Microsoft Natural PS/2 Keyboard with HP QLB
input.2.keyboard.1.name=\\?\ACPI#PNP0303#4&4112574&0#{884b96c3-56ef-11d1-bc8c-00a0c91405dd}
input.2.keyboard.1.empty=false
input.2.keyboard.1.disabled=false
input.2.keyboard.2.friendlyname=WinUAE null keyboard
input.2.keyboard.2.name=NULLKEYBOARD
input.2.keyboard.2.empty=false
input.2.keyboard.2.disabled=false
input.2.keyboard.3.empty=true
input.2.keyboard.4.empty=true
input.2.keyboard.5.empty=true
input.2.keyboard.6.empty=true
input.2.keyboard.7.empty=true
input.2.keyboard.8.empty=true
input.2.keyboard.9.empty=true
input.2.keyboard.10.empty=true
input.2.keyboard.11.empty=true
input.2.keyboard.12.empty=true
input.2.keyboard.13.empty=true
input.2.keyboard.14.empty=true
input.2.keyboard.15.empty=true
input.2.keyboard.16.empty=true
input.2.keyboard.17.empty=true
input.2.keyboard.18.empty=true
input.2.keyboard.19.empty=true
input.2.internal.0.friendlyname=Internal events
input.2.internal.0.name=INTERNALEVENTS1
input.2.internal.0.empty=true
input.3.joystick.0.empty=true
input.3.joystick.1.empty=true
input.3.joystick.2.empty=true
input.3.joystick.3.empty=true
input.3.joystick.4.empty=true
input.3.joystick.5.empty=true
input.3.joystick.6.empty=true
input.3.joystick.7.empty=true
input.3.joystick.8.empty=true
input.3.joystick.9.empty=true
input.3.joystick.10.empty=true
input.3.joystick.11.empty=true
input.3.joystick.12.empty=true
input.3.joystick.13.empty=true
input.3.joystick.14.empty=true
input.3.joystick.15.empty=true
input.3.joystick.16.empty=true
input.3.joystick.17.empty=true
input.3.joystick.18.empty=true
input.3.joystick.19.empty=true
input.3.mouse.0.friendlyname=Windows mouse
input.3.mouse.0.name=WINMOUSE1
input.3.mouse.0.empty=true
input.3.mouse.1.friendlyname=HID-konforme Maus
input.3.mouse.1.name=\\?\HID#VID_05FE&PID_0011#6&1f02c73c&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}
input.3.mouse.1.empty=true
input.3.mouse.2.friendlyname=Synaptics PS/2 Port TouchPad
input.3.mouse.2.name=\\?\ACPI#SYN014B#4&4112574&0#{378de44c-56ef-11d1-bc8c-00a0c91405dd}
input.3.mouse.2.empty=true
input.3.mouse.3.empty=true
input.3.mouse.4.empty=true
input.3.mouse.5.empty=true
input.3.mouse.6.empty=true
input.3.mouse.7.empty=true
input.3.mouse.8.empty=true
input.3.mouse.9.empty=true
input.3.mouse.10.empty=true
input.3.mouse.11.empty=true
input.3.mouse.12.empty=true
input.3.mouse.13.empty=true
input.3.mouse.14.empty=true
input.3.mouse.15.empty=true
input.3.mouse.16.empty=true
input.3.mouse.17.empty=true
input.3.mouse.18.empty=true
input.3.mouse.19.empty=true
input.3.keyboard.0.friendlyname=HID-Tastatur
input.3.keyboard.0.name=\\?\HID#HPQ0006&Col02#3&1f5eafa&0&0001#{884b96c3-56ef-11d1-bc8c-00a0c91405dd}
input.3.keyboard.0.empty=false
input.3.keyboard.0.disabled=false
input.3.keyboard.1.friendlyname=Standard 101/102-Key or Microsoft Natural PS/2 Keyboard with HP QLB
input.3.keyboard.1.name=\\?\ACPI#PNP0303#4&4112574&0#{884b96c3-56ef-11d1-bc8c-00a0c91405dd}
input.3.keyboard.1.empty=false
input.3.keyboard.1.disabled=false
input.3.keyboard.2.friendlyname=WinUAE null keyboard
input.3.keyboard.2.name=NULLKEYBOARD
input.3.keyboard.2.empty=false
input.3.keyboard.2.disabled=false
input.3.keyboard.3.empty=true
input.3.keyboard.4.empty=true
input.3.keyboard.5.empty=true
input.3.keyboard.6.empty=true
input.3.keyboard.7.empty=true
input.3.keyboard.8.empty=true
input.3.keyboard.9.empty=true
input.3.keyboard.10.empty=true
input.3.keyboard.11.empty=true
input.3.keyboard.12.empty=true
input.3.keyboard.13.empty=true
input.3.keyboard.14.empty=true
input.3.keyboard.15.empty=true
input.3.keyboard.16.empty=true
input.3.keyboard.17.empty=true
input.3.keyboard.18.empty=true
input.3.keyboard.19.empty=true
input.3.internal.0.friendlyname=Internal events
input.3.internal.0.name=INTERNALEVENTS1
input.3.internal.0.empty=true
input.4.keyboard.0.friendlyname=HID-Tastatur
input.4.keyboard.0.name=\\?\HID#HPQ0006&Col02#3&1f5eafa&0&0001#{884b96c3-56ef-11d1-bc8c-00a0c91405dd}
input.4.keyboard.0.custom=true
input.4.keyboard.1.friendlyname=Standard 101/102-Key or Microsoft Natural PS/2 Keyboard with HP QLB
input.4.keyboard.1.name=\\?\ACPI#PNP0303#4&4112574&0#{884b96c3-56ef-11d1-bc8c-00a0c91405dd}
input.4.keyboard.1.custom=true
input.4.keyboard.2.friendlyname=WinUAE null keyboard
input.4.keyboard.2.name=NULLKEYBOARD
input.4.keyboard.2.custom=true
Reth is offline  
Old 28 May 2015, 08:13   #12
Toni Wilen
WinUAE developer
 
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,514
Config looks ok. uaescsi.device getting automatically enabled can only happen if CDFS automount is also enabled (but it isn't in your config).

Load your config, enable logging, start emulation, wait until pink screen appears, enter gui, paths panel, save both config and winuaelog.txt using path panel options. (This config is the actual in use config after possible automatic fixups).

EDIT: Very important: Quit WinUAE completely and then restart it. Never load any config on the fly, always quit completely when testing!

Last edited by Toni Wilen; 28 May 2015 at 13:53.
Toni Wilen is offline  
Old 28 May 2015, 19:17   #13
Snake79
Registered User
 
Join Date: Feb 2014
Location: Poland
Posts: 190
@Reth
Here you are (configs). I have used them to install AOS4.1FE few days ago (on latest betas of WinUAE).
Attached Files
File Type: uae OS4.1 A4000 PPC JIT 128MB PicassoIV SCSI.uae (20.7 KB, 429 views)
File Type: uae OS4.1 A4000 PPC JIT 128MB PicassoIV IDE.uae (20.7 KB, 388 views)
Snake79 is offline  
Old 17 June 2015, 17:03   #14
Reth
Registered User
 
Join Date: Feb 2015
Location: Germany
Posts: 64
Thanks Snake79 and also to all others.

Got it working meanwhile and installed AOS4.1FE. Unfortunately it lacks on main memory. Is there any way to provide more RAM using WINUAE (already tried several settings - with no success). Or would it work to at least provide a SWAP partition?
Reth is offline  
Old 18 June 2015, 13:46   #15
mikettl
Registered User
 
Join Date: Aug 2014
Location: Boston
Posts: 36
@Snake79
I run also in problems with the endless boot loop, but after using your posted A4000 WinUAE configuration file I was immediately able to install AMigaOS41. Great, many thanks for your effort and support :-).

@All
after installation i have just 2 question, probably some of you guys made the same experiences:

Memory: in WinUAE additional 256 MB Z3 Fast RAM is configured (beside the 128 MB in the processor slot), but AmigaOS recognizes only 128 MB. Is there a possibility to fix this?

Screen Mode: I'm using an external LCD monitor at my laptop, the emulation runs in full screen mode. However the monitor can handle 1600x900 but the screen mode in AmigaOS allows me only 1280x720 to configure (1280x960 is possible as well but I like more the wide screen appearance). Is this maybe limited to the PicassoIV limited?

Sorry, maybe rookie questions...

Another strange effect I got yesterday after installation: after rebooting AmigaOS 4.1 the screen kept black and never came back to the Workbench. After trying it this morning again, all worked fine. The only difference is that yesterday I made the final configuration on the laptop screen (w/o external monitor). Did someone else had this sometimes?

Many thanks and best regards
Mike
mikettl is offline  
Old 19 June 2015, 13:51   #16
Toni Wilen
WinUAE developer
 
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,514
Quote:
Originally Posted by Reth View Post
Got it working meanwhile and installed AOS4.1FE. Unfortunately it lacks on main memory. Is there any way to provide more RAM using WINUAE (already tried several settings - with no success). Or would it work to at least provide a SWAP partition?
No. OS4 kernel change is needed.

Quote:
Memory: in WinUAE additional 256 MB Z3 Fast RAM is configured (beside the 128 MB in the processor slot), but AmigaOS recognizes only 128 MB. Is there a possibility to fix this?
No, see above.

Quote:
Screen Mode: I'm using an external LCD monitor at my laptop, the emulation runs in full screen mode. However the monitor can handle 1600x900 but the screen mode in AmigaOS allows me only 1280x720 to configure (1280x960 is possible as well but I like more the wide screen appearance). Is this maybe limited to the PicassoIV limited?
4M VRAM hard limit. Try reducing number of colors. (from true color to high color). Only way to "fix" this is to emulate some supported display card that supports more than 4M VRAM.

Quote:
Another strange effect I got yesterday after installation: after rebooting AmigaOS 4.1 the screen kept black and never came back to the Workbench. After trying it this morning again, all worked fine. The only difference is that yesterday I made the final configuration on the laptop screen (w/o external monitor). Did someone else had this sometimes?
Without log (winuaelog.txt) it is impossible to say what happened.
Toni Wilen is offline  
Old 22 June 2015, 04:11   #17
mikettl
Registered User
 
Join Date: Aug 2014
Location: Boston
Posts: 36
Quote:
Originally Posted by Toni Wilen View Post
No. OS4 kernel change is needed.
4M VRAM hard limit. Try reducing number of colors. (from true color to high color). Only way to "fix" this is to emulate some supported display card that supports more than 4M VRAM. ...
Without log (winuaelog.txt) it is impossible to say what happened.
Thx Toni :-)
mikettl is offline  
 


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools

Similar Threads
Thread Thread Starter Forum Replies Last Post
AmigaOS 4.1 boot up adf xboxown support.WinUAE 7 18 October 2014 15:37
Create dual boot (AmigaOS/AmigaSYS) CF card with WinUAE JackTheKnife support.WinUAE 14 29 November 2012 06:00
AmigaOS and Amiga4SYS dual boot CF card JackTheKnife support.Hardware 3 14 December 2010 00:53
CF card and dual boot (AmigaOS/AmigaSYS) JackTheKnife support.Hardware 34 03 January 2010 03:52
can you install amigaOS on the a600 without memory expansion? sanDae New to Emulation or Amiga scene 26 03 March 2009 15:40

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT +2. The time now is 01:05.

Top

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.
Page generated in 0.09147 seconds with 16 queries