---snip---

No longer an issue.

@sofistisoftware

Thanks again for the temporary fix. Disabling the rear USB ports ended a real nightmare. My MicroA1 is running just fine now with OS4.1 Update 1.

I will play with kicklayout when I return from my business trip in 2 weeks.

---
redfox
MicroA1-C with 750 GX and 256 MB RAM
AmigaOS 4.1 Update 1

Update ... Temporary fix ... disabled rear USB ports on MicroA1

Original post ...

Most of the time, I get a white workbench screen when I boot from my CD-R.

When my system finally booted into the screen where you can choose what you want to do my system froze.

MicroA1 with 750 GX CPU and 256 MB RAM

I have not formatted my system partition yet because I think I should at least be able to boot into something usable from the CD.

---
redfox

@JOS

This is the first change I make every time I upgrade to a new version of OS4 on my MicroA1 since (I think it was) OS4.0 update 4. I use DHCP on my router with all my PC's and my MicroA1.

Run >NIL: C:AddNetInterface QUIET DEVS:NetInterfaces/~(#?.info)

I think maybe the OS4 team are suggesting that we should not touch the startup-sequence because it may cause issues with troubleshooting later if we forget what changes we have made.

edit to explain ...

My needs are very simple. I don't have any programs that want to access the net immediately after booting up the machine (other addinterface of course).

My User-Startup file contains a bunch of assigns and some setenv commands.

My WBStartup contains RAWBInfo, AsyncWB, DefIcons, ClickToFront, AmiDock and AISS.

When I want to use a web browser, WookieChat, SimpleMail, YAM, or AmigaExplorer, I launch the required application separately as needed after the Workbench Screen comes up.

---
redfox

@joerg

I am very impressed with OWB 3.22 so far. Working very well on my MicroA1 with AmigaOS 4.1. No complaints whatsoever.

Thanks,
redfox

Posting with OWB 3.22 right now. I have only had it installed for about 15 minutes, so will reply again later after some surfing.

---
redfox

Using OWB 3.21 right now. Working fine so far.

Thanks Joerg.

redfox

@TrevorDick

Here is a 'quick and dirty' test I just performed using a CD-R containing a complete system backup.

I am using the AmigaOS4PPC version of E-UAE 0.8.29.WIP3-SDL.

I copied the uae-sdl program and my .uaerc file to Ramdisk and made a few changes to the .uaerc file to access required files on my CD-R.

I double-click on the uae-sdl program icon in Ramdisk and it uses the modified .uaerc file to find the rest of my AmigaOS 3.1 system on the CD-R.

On my CD, I have a drawer called E-UAE.
In that drawer, I have my, Kick.rom file and Workbench drawer.
The Workbench drawer contains a complete set of AmigaOS 3.1 system directories.

I have modified the .uaerc file to the following to access the required files on my CD-R disc:

# UAE Configuration File for Amiga OS 4.0 pre-release update #4
# E-UAE 0.8.29-WIP3 SDL
# emulating NTSC Amiga 2000HD with Amiga OS 3.1
#

kickstart_rom_file=CD0:E-UAE/Kick.rom

filesystem2=rw,DH0:Workbench:CD0:E-UAE/Workbench,1

joyport0=mouse
joyport1=kbd1

cpu_type=68000

chipset=ecs_agnus
ntsc=true
cpu_speed=max
cpu_compatible=no
cpu_24bit_addressing=no
chipmem_size=2
fastmem_size=4
gfx_fullscreen_amiga=true
gfx_fullscreen_picasso=yes
gfx_linemode=double
gfx_width=640
gfx_height=480
gfx_center_horizontal=true
gfx_center_vertical=true

---
redfox

Of course, I can't save anything from AmigaOS 3.1 because the CD-R is read only, but at least it proves a concept. You could find the correct directories on the AmigaForever CD and fill in the blanks for

kickstart_rom_file=CD0:<path>
and
filesystem2=rw,DH0:Workbench:CD0:<path>
and
kickstart_key_file=CD0:<path>

@TrevorDick

I have been using E-UAE 0.8.29-WIP3 SDL for a long time now.

I am not using the AmigaForever package, so there may be some differences. In my case there is no key file.

This is my configuration on my MicroA1 hard drive
I have a directory called E-UAE on my main OS4 system partition.
Inside that directory, I have the uae-sdl program, .uaerc file, Kick.rom file, a Workbench directory and a directory called ADFs.

The Workbench diectory contains a complete set of AmigaOS 3.1 system directories (from Workbench3.1 disk and Extras3.1 disk)

When I launch uae-sdl, it uses the .uaerc file and Kick.rom, as well as the startup-sequence, user-startup, fonts, libs, etc from my AmigaOS 3.1 Workbench directory.


My .uaerc file .....

# UAE Configuration File for Amiga OS 4.0 pre-release update #4
# E-UAE 0.8.29-WIP3 SDL
# emulating NTSC Amiga 2000HD with Amiga OS 3.1
#

kickstart_rom_file=SYS:E-UAE/Kick.rom

filesystem2=rw,DH0:Workbench:SYS:E-UAE/Workbench,1

joyport0=mouse
joyport1=kbd1

cpu_type=68000

chipset=ecs_agnus
ntsc=true
cpu_speed=max
cpu_compatible=no
cpu_24bit_addressing=no
chipmem_size=2
fastmem_size=4
gfx_fullscreen_amiga=true
gfx_fullscreen_picasso=yes
gfx_linemode=double
gfx_width=640
gfx_height=480
gfx_center_horizontal=true
gfx_center_vertical=true

---
redfox

@DAX

Like ChrisH, I always keep a previous version as a fallback if things go wrong. OWB 3.19 worked just fine for me once I discovered how to change the default search engine to altavista. OWB 3.20 is working just fine for me. Now that I can use google again, I have removed all previous versions, including OWB 3.19.

Even though we have some Windows machines here at home, I use my MicroA1 for 99% of all my web browsing. I have gotten used to using google as my default search tool and that is why I made such a fuss about the crashes with OWB. OWB 3.20 has not crashed at all since I installed it and that makes me very happy.

---
redfox

Posting with OWB 3.20 right now. No further issues with Google search. I can go back to the search list just fine with no crashes.

Nice extra features in the menu.

Thanks Joerg.

redfox

OWB 3.19 has been working fine for me since I changed the default search setting to use AltaVista instead of Google. I've been using it this way for quite a few days.

---
redfox

@redfox

Interesting .......

If I go into tool types, there are two search sites in brackets.

If I get rid of the google.com one and force the other one to be active, no further crashes.

SEARCH=http://exalead.com/search/results?q=%s

As far as I know, I have never used exalead.com before for searches.

It seems to create a listing with pictures. Since I have never used this site before, I don't know if these pictures are similar to icons or if theyare some sort of graphical link to the listed website. They look sort of like a shrunken version of the front page of the linked website. I can click on any link and go to the web page ok and return to the listing ok when I click the back arrow button.

[edit...]
Yahoo.ca search also seems to work ok, although a bit slower,
SEARCH=http://ca.search.yahoo.com/search?p=%s

---
redfox

@TSK

Any one of the following search terms should cause a crash:
soyuz
avro arrow
rose
tiger

For example, type rose in the text entry area at the top right corner of the OWB window. Hit enter key. Google search should create a list with some pictures. Click on any one of the links. You should be able to see that web page ok. Then click on the back arrow at the top left corner of the OWB window and you should see a crash.

Note:
I am using default settings for OWB 3.19.
I have a MicroA1 with IBM 750 GX CPU and 256 MB RAM.
I am using publically released versions of AmigaOS 4.1 and Quickfixes.
(no beta versions)

---
redfox

@MickJT

See my crash log 273 over at http://crashlog.os4depot.net/.

Not sure if I can report a bug at the bug site.

---
redfox

@Alkaron

Thanks for pointing that out. You are right. I get a crash every time I go back to a google list with pictures. I had so many crashes last night that I did not realize that one search worked just fine. It had no pictures.

For example, if I enter any one of the following search terms, I get a crash when I go back to the list:
soyuz
avro arrow
rose
tiger

If I use the following search term, I get a list with no pictures and no crash:
aminet
the digital group

For the benefit of anyone else who is trying to duplicate the crash ...

I enter my search term (for example, the word soyuz) in the text field in the upper right corner of the OWB window beside the magnifying glass and press the enter key. Google does a search and creates a list. Usually I can click on a link in the list and the web page comes up ok. Then when I click the back button in the upper left corner of the OWB window, the program crashes.

The crash seems to occur if there are pictures in the original list generated by Google.

---
redfox

Repeat issue from OWB 3.18 and maybe some previous versions ...

OWB 3.19 crashes going back to a list generated by google search.

I search for any subject with google search (the default search engine for OWB) and I get the list ok. Click on one of the links (such as the wikipedia page) and it usually goes there ok. Click the back arrow to go back to the list and OWB crashes. Does not seem to matter which entry I choose from the list. The only way I can get rid of the frozen OWB window is to reboot my computer.

I do not mean to be nasty here, but surely doing searches with a web browser is a normal activity. I can do a similar search with AWebPPC (AWeb APL Lite) and IBrowse and they do not crash when I go back to a list generated by the google search.

---
redfox
MicroA1
AmigaOS 4.1

@orgin

Posting with OWB 3.19

@LiveForIt

Perhaps OWB does not like to display pure text files.

If I try to disply the usb.log file using OWB 3.15, the program crashes. At least I don't get anything with OWB 3.18. I am using default settings.

Just for fun I popped an html file into ram:t and I can see it just fine with OWB 3.18.

file:///ram:t/myfile.html

file:///ram/t/myfile.html

---
redfox

@orgin

Posting with OWB 3.18 right now. Wordwrap issue is still there when I am typing into the textarea form at amigans. Now that I am used to part of the word on the previous line and the rest on the new line, it does not bother me anymore.

I will report again after I have surfed around the net for awhile.

---
redfox