@TCD

When you'll get your Sam I hope you will take a lot of pictures of your project for us !?

@Troels
Quote:
Have you tried already if you can fit Sam board inside those old notebooks or are they too small (if you have your Sam yet) ?

@+Antique
Quote:
Maybe mr. Schoenfelder could make a new Keyrah for us !? Or maybe somebody could hack an USB interface into that laptop keyboard interface.

@joerg

Are you going to make a new shared objects version of OWB someday too ? (No hurry.)

@AmiKit

Quote:
I have LG 204. Make sure your monitor has recognized the screen mode correctly and do that auto adjust then again. If it hasn't recognized the screen mode and you have an input switch in your monitor try switching between analog and digital inputs as many times as is required it to recognize correct screen mode. Or open another screen on your Amiga which has different resolution than Workbench and switch between those screens as many times is needed your monitor to recognize the screen mode. Or if you have a Linux/Winblows box (or Linux installed on your Amiga) you could try to use them to adjust your monitors settings and then switch back to your Amiga (and don't touch auto adjust button ever again .

Quote:
DVI works perfectly with AOS4.1. I don't have any problems with it.

@AmiKit

Add this: MODE=1680x1050@60 line to the tooltypes of your DEVS:Monitors/Radeon. Check also these:
VSYNCMIN=
VSYNCMAX=
HSYNCMIN=
HSYNCMAX=

that they're matching values in the manual of your monitor (so you won't break your monitor).

At least DVI works on AmigaOne and Debian. And I don't remember tweaking any settings for that.

What's wrong putting AmigaOS and Linux on the same hard drive ?

Quote:
And me as well. I don't like these Facebooks and Myspaces. But creating a group for Amigans is actually a good and nice idea.

@ChrisH
Quote:
No. Somebody posted a direct hyperlink to that file in AW.net. I downloaded it without signing anything. And it looks there's some tools (don't remember exactly, was there gcc) which might be under GPL, so if there's any GPL stuff then it should be freely available to everybody. The most of the stuff in that SDK uses Mingw on Winblows. Only a couple of executables are Winblows executables but you can run them fine with Wine.

@TSK

Doh, doh and doh once more. I was testing Ranger yesterday and checked what all kind of things I have on my system. I happened to look what I have in ENVARC: and ENV: and I found I had some big files there generated by my experimental piece of software I was developing some time ago. I removed those unnecessary big files. Now I have fast booting times and I have also more than 100 MB more free RAM after booting. I'm quite embarassed to tell all this because I'm suppose to be an experienced computer user. I forgot those files. So the system was slowed down because IPrefs was copying large files to ENV: (RAM). Yes I know, it was bad habit to put such files into ENVARC: in the first place. (Btw. That experimental app was a file indexing tool.)

I remember someone saying on forums that that behaviour have changed in AmigaOS lately. In older AOS versions files were copied to ENV: only when some program tried to access them. Is it really changed back to such behaviour that all ENVARC: stuff is always fully copied to ENV: at boot time ?

I've wanted to start a new thread for this. But some time ago people were storing all kinds of config files to S: which is wrong place because it's for scripts. Then people, like myself, started to put config files to ENVARC: which is wrong place many times too. So could it be possible to add a new directory, called "config" f.ex., to the standard directory structure of the AOS where people could store all config files ? Or is Prefs directory a good place to store them ? What do you think ? Some people are putting some files to DEVS: which I think is not always right place for them either.

I haven't tested cold boot time yet but soft boot is now 15 secs everything loaded (WB + AmiDock + everything).

@Troels
Quote:
I looked that AA2 SDK and their programming "language"/system looks quite simple (but powerful). Google Android uses Java and Java looks very complicated to newbies or people who can't use anything more complicated than Basic. But AA2 is simple and you have to write very few lines of code to make a fully working game f.ex. They have (had when I looked) some things missing but when it's finished it's not bad. It's much better than Android f.ex. IMHO.

@Capehill

I get random freezes and hard reset is required. Impossible to play.

How much free RAM does it need ?

@TSK

Here's one more. Anytime I quit MEmacs all my apps iconifies and deiconifies themselves. They accept/read SNOTIFY_AFTER_OPENWB and SNOTIFY_BEFORE_CLOSEWB messages only. That's annoying. (I don't know if this is related to the old SDK.)

@tonyw

What about my second problem: Colours of the non-WB pub screens are wrong after DisplayBeep() (f.ex. when typing non-accepted characters in file requesters) ? Did you make a bug report for that too ?

I uploaded two bookmarks related and one fastlink app in single OWBBook archive to os4depot a week ago. Not because there's anything wrong with other implementations. But I wanted to be able to use IBrowse's bookmarks directly. And also I wrote them in C so they start fast and are small in size.

@joerg
Feature request: When OWB starts the bookmarks app it would be nice if it would give the name of the public screen where OWB is opened as an argument also.

@tonyw
Quote:
Yes, I did. Using the mode 1680x1050 but setting screen size to 1696x1056, screen was cleared correctly. I tested even makeing 1696x1056 screen mode and using that mode in another pub screen. I think my monitor didn't like it. The whole screen was s***wed and there were random stripes, strange colours and everything. But when I took a screen grab with Sgrab that "sgrabbed" picture was perfect. (But when using 1680x1050 mode and the screen is not cleared it looks same in both sgrabbed picture and reality.)

I think making it possible to set backdrop of any public screen in screen prefs would be nice work around. Because setting the background would clear it

@abalaban

Quote:
And doing nitpicking. SE has soldered CPU, no module.

@vodkasoda

It would help a lot if you told us more information. Do you have a hard drive installed to your computer or do you boot from a floppy ? Which Kickstart ROM's (version number) do you have ? And if you boot from a hard drive, which AmigaOS version do you have installed on your hard drive ? Do you have any turbo card installed to your computer ?

@vodkasoda

Do you have any CDROM drivers installed ? If you have Amiga OS (Kickstart+Workbench) version older than 3.5 you have to install drivers for your CDROM device.

@caver99

Read the FDTool.doc in the OS4.0 "Documentation" drawer. (I don't remember in which OS4 version a1floppy.device came with the first time. OS4 Final ?)

Quote:
I think you can.

@COBRA

Quote:
Like I said already:
Quote: ("Older DVD's" means region code 2.)