@nubechecorre

Quote:

Yes pretty please, as then I can resurrect my 1200/PPC that is taking dust since my A1XE arrived in house almost 3 years ago

@Chris

Radeon 9200 SE 128 MB

13 0x1002 0x5964 ATI Technologies RV280 Radeon 9200 SE Series
14 0x1002 0x5D44 ATI Technologies RV280 Radeon 9200 SE Series - Secondary

A1XE

@agafaster

Quote:

did you try usbctrl restart ?

For my USB stick this is the opposite : I have no choice to leave it at boot time (cold or warn) else it is not recognized or I have to restart the USB stack.

@nubechecorre

First don't you think you'll get much more answers on the AWeb ML instead ?

Second did you do something on your *AWEB* cache lately ? Try to squeeze it completly an dtry again.
The "two times" refresh might be caused by the "fast answer" option (see the doc for correct configuration, depending on your connection speed). It can also be caused by your image decoder configuration, progessive array display option, the size of the cache, etc.

BTW you didn't even provided the AWeb version you are using, knowing it could help answering you because many bugs was fixed during versions updates (some were related to display).

@LiveForIt

Quote:

In fact that's simple : take your all-in-one printer (printer+scanner function).
Using USB naming it's a 'Function', now as it has multiple features, it shows them to the system in the form of two 'Interfaces' (one for the Printer functionnality, one for the scanner functionnality).
(another example is a mouse/keyboard combo using one USB port, it also provides two interfaces : one for the keyboard, one for the mouse)

Now back to the stack driver : say you want to write a driver for your printer to be able to print and scan.
You have the choice to write a 'Function driver', that is a driver that will take control of the whole hardware, or an 'Interface Driver' which will take control of one Interface.
In our example you would have to write one Function driver, or two Interface drivers (one for the printing interface, one for the scan interface).
The advantage of writing Interface drivers is that you concentrate on one functionnality, leaving the opportunity for other Interfaces drivers to take care of other interfaces presented by your hardware.
In our example, OS4 already comes with an USB printer driver, so you can already print with your all-in-one printer, it would be stupid to write a Function driver in this case because then you would have to write the printer part as this will prevent the OS4 default driver to acces it
To sum up prefer writing interface drivers instead of Function driver this is more friendly and also you divide the work to do.

@aldur

Quote:

Did you tried the email on this page ?

@salass00

Then popup Exchange, find and select ScreenBlanker in the list, then click on "Deactivate". Your screenblanker is deactivated, you can play alien breed

@chris
Application.library has a "enter game mode"/"exit game mode" which should be used by any new program, this would benefit the whole system IMHO because every interested registered soft will be notified of that.

@olsen

Even if I did not have the problem myself, I've found interesting to read your posts here. They are what we are missing this time on forum, thank you.

@Hans

Quote:

I don't agree here, in fact the path taken by Switcher3D's author is the good one. To have the desired effect, you only need to :
1) take a snapshot of each window
2) close all opened windows
3) display those snapshots in what ever style (be it in a 3D, vista like, or anything other) in a transparent window
4) provide a way to select of the presented snapshot
5) reopen all previously opened windows (in the same order/place)
6) take to front the window corresponding to the selected snapshot

None of this functions need to patch, hack, replace or anything else system's functions. I see no reasons why you should patch the system by less stable functions, let it be independant and if it ever crash then you could always go on using your system...

Very good idea from the author, now it's obvious, but I must admit I wouldn't have had the idea myself !

@spotUP

No this this "just" TCL, which is in fact a powerful scripting language. Tk is an independant addon to TCL which offers TCL programs a GUI system upon X11. As it was designed by amost the same people they were often associated under the name "Tcl-Tk" but they are really two different things.
I have not looked at it, but I think Tk should be more difficult to port, because you'll have to write many wrappers to replace X11 calls...
I don't think I'll look at it, I don't have time to do it.

@spotUP

I'm working on it... Will see what I can do, I think it's possible.

@AmiGame

it was openOffice which in fact reveal to be a big bmp image...

@LiveForIt

Thank you for your answers. After some little more researches I have found that the fork() call is really only used to spawn a child process that will then be used to execute (via execvp()) a specified command asynchronously (after having redirected I/O to a previoulsy opened pipe, was using pipe() call that I replaced by opening a unique file in PIPE: one with read access, one with write access).
However nothing prevents from launching several childs at the same time, so I can't rely on the use of global variables.

Then as I said a wait() call is made to gather alll terminated childs process to prevent them from becoming zombies and also to eventually generate error message in case child terminated abnormaly (signaled, return code). Currently I'm much more looking at the struct DeathMessage that can be sent automatically, someone already used that ? Suggestions ?
The wait() replacement is not strictly needed because under AOS we can make the spawned process terminate itself without interfering with the parent, however if we want to have the return code, we have no choice than to keep track of all spawned childs and to analyse their return code at termination time.

@ssolie

In fact the fork() is followed by an execvp() however it does not waitpid() immediatly (i.e. read the call is asynchronous and checked later).
However as it does not rely on features of the fork() I think it can be replaced by a SystemTags() call or by a CreateNewProc() however I'm new to Amiga processes coding so don't know how I could simulate the wait() call. I don't know however if it's really needed or if it's here only for cleaning the killed process to prevent it from becoming a zombie, I should check that...

For one of my projects I have to use the TCL library, however this has not been ported to OS4 yet (and the 68k one does not work either).
I tried to recompile it directly but that did not work : TCL rely on some *ix functions that are not available in the currently supported C runtime (most problematic ones beeing fork() and wait()) so to have an OS4 native port of TCL this should be done "cleanly" by adding the support for the Amiga platform.
Did(does) someone work on that is interested in it ? Currently I managed to remove mainly every *ix dependencies, it remains only fork(), wait() and tzset(). I think this can be done relatively easily because the fork() call is immediatly (just a few lines) followed by an execvp()...
I don't think I'll have the time to finish it right now and thought maybe someone else already work on it or would be interested in doing it ?

PS: of course I'll provide my current sources if someone is interested to go on.

@salass00

I also looked at PasTex (that I used under OS 3.9 with the WOS version to write my end course report) to port it under OS4, however I did not go much ahead either I would find it very usefull to have latex on OS4 with all its latest packages available.

@COBRA

The "silence" is not only Hyperion side, there is plenty of silence everywhere these days, I would have sworn I once heard my echo last time I posted

Just kidding, I think this comes from the fact that first Quarter is coming to end and everybody is crossing fingers for really good news both on the hardware side and on the OS4 side (in the way of a port to this hardware).

@COBRA

Free OS4 compatible hardware ?

@abalaban

Again removing the DEFER argument just cured the problem or else someone did changed something on this site ??
Thank you Raziel for the idea

@Raziel

Ok I can't reproduce it anymore, does anyone changed something on the site ? Or was it the DEFER option to assign that did not work ?