Login
Username:

Password:

Remember me



Lost Password?

Register now!

Sections

Who's Online
51 user(s) are online (38 user(s) are browsing Forums)

Members: 1
Guests: 50

VooDoo, more...

Headlines

Forum Index


Board index » All Posts (Dragster)




Re: Dopus5 call for test: fix of mui freezes
Just popping in
Just popping in


@Kas1e

Tested with YAM and OWB on Peggy II as well ..No freezes!! Thank you!

Go to top


Re: Kas1e a video for you
Just popping in
Just popping in


@tlosm

Interesting... how did you connect a radeon 9800 PRO to the Pegasos?

Go to top


Re: Odyssey 1.23 progress
Just popping in
Just popping in


@kas1e

Awesome, great work man. Thanks for your efforts on porting Oddyssey to OS4!

Cheers,

Dragster

Go to top


Re: Flipclock V53.2 released
Just popping in
Just popping in


@Phantom

Yes, it doesn't work here either!

Go to top


Re: fxscan 4.0
Just popping in
Just popping in


Hi there, yes.. I've got it.. check your email in a couple of hours

Cheers,

Dragster

Go to top


Re: fxscan 4.0
Just popping in
Just popping in


Quote:

JosDuchIt wrote:
Can the update ffrom fxscan 4.0 to fxscan 4.06 ne downloaded somewhere?


I can email it to you, PM me.

Cheers,

Dragster

Go to top


Re: Opus Magellan source is free now!
Just popping in
Just popping in


Your work is very much appreciated folks, thank you!

Go to top


Re: Opus Magellan becomes free
Just popping in
Just popping in


@ChrisH

Quote:

While an OS4 version of Opus Magellan would be really nice, I'd still prefer to have a more up-to-date port of OWB-MUI...


I really appreciate kas1e's efforts on the Amiga camp but I'd rather have an updated version of MUIOWB as well.

Very good news though :)

Cheers,

Dragster

Go to top


Re: Jack: Check for avail memory; Everyone help please
Just popping in
Just popping in


AmigaOS 4.1 Update 3 Workbench 53.7 Kickstart 53.22
Saturday 08/10/11 11:30
9.RAM Disk:> c:avail
Installed: 2147483648
Free: 1576079360
9.RAM Disk:>

Go to top


Re: Some info leaked from AmiWest
Just popping in
Just popping in


Hi,

I'm glad you guys took a look to my report... yep, it was me who noticed those new options in some of the preference programs of AmigaOS4.1 beta (update 3?)... I'm quite happy that I'll be able to get rid of that awful gray background color and turn it to black among other things...


Cheers,

Dragster

Go to top


Re: SabreMSN 0.64 DSI's on SAM and 4.1.1?
Just popping in
Just popping in


@jahc

Yes, solved on my system also

Thank you!

Go to top


Re: SabreMSN 0.64 DSI's on SAM and 4.1.1?
Just popping in
Just popping in


@tommo1975

Yes, it also happens here. Pegasos II G4 with OS4.1 Update 1. Thanks for submitting that crashlog, hopefully this will get fixed soon.

Cheers,

Dragster

Go to top


Re: OS4.1 Update 1 problems & solutions
Just popping in
Just popping in


Hi all,

just to let you know that I've solved my issue with WET forecaster app docky icon.

I've reverted to WBStartup functionality by deleting wbstartup.prefs and creating the wbstartup directory, then I copied all the needed applications, just like usual prior to this version, tweaked start the start priority on both amidock and wet icons so that wet is forced to start after amidock and voil?, problem solved...

@Chris

This solution would work for WifiSignal icon too if you don't care reverting to the old style wbstartup method.

Thanks for the suggestion though, I'll stick to the good old wbstartup directory method

Cheers,


Dragster

Go to top


Re: OS4.1 Update 1 problems & solutions
Just popping in
Just popping in


@Chris

Argh! An annoying bug, isn't it? Should we wait for an amidock fix then or updated versions for these programs with workarounds?

Cheers,

Dragster

Go to top


Re: OS4.1 Update 1 problems & solutions
Just popping in
Just popping in


Hi All,

I've installed this great update it on my Peg II.. I'm almost done migrating apps and such.. but I found a little problem with WET forecaster.. docky app icon won't come up in amidock if both commodities are loaded from wbstartup prefs at boot, it only shows up if I start WET after amidock is running...

I've tried to change the order in wbstartup prefs to start amidock before WET but no go.. replaced the amidock exe with the one from OS4.1 (no update) and that one works fine...

Any ideas?

Thanks!

Dragster

Go to top


Re: OWB 3.22 + New features
Just popping in
Just popping in


@samo79

Updated via Amiupdate.. working dine so far,

thanks J?erg!

Go to top


Re: Have you interest to have "putty" for os4 ?
Just popping in
Just popping in


@kas1e

I use putty everyday! I'd certainly love to have it ported to OS4, please do!

Thank you!!

Go to top


Re: SabreMSN 0.58 - 2009-08-24 - Multiple accounts support/login window
Just popping in
Just popping in


Thanks jahc for this new version. However it seems* renaming contacts doesn't work anymore...

Anyone else having this problem?

Cheers

Go to top


Re: 24" monitors.. 1920x1080 or 1920x1200 ?
Just popping in
Just popping in


@bean

I use a 22.5'' BenQ monitor @ 1920x1080 which has both HDMI (for my PS3 - true 1080P) and standard VGA and DVI inputs (for my PC / Amiga).

Interesting.. looks like what I need ... what's the exact model #?

Cheers!

Go to top


Re: OS4 classic video problems in high res. screen modes.
Just popping in
Just popping in


@Raziel

H!

Quote:

Ok, first of all, which monitor do you use?
(and are you sure the settings go conform with it?)


I'm using a Daewoo 19" Flatscreen CRT monitor. The settings of the monitor are set according to the monitor's owners manual.

Quote:

Second, the BVision can only handle screenmodes upto
1152 x 900, 24Bit, 75 Hz
1600 x 1200, 16Bit, 72 Hz max, which means, you should try
the following Monitor prefs (taken from here)


Actually, that's a theorical limit, it can handle much more than that.

Quote:

For Screenmodes higher than that, no guarantee is given
that it will work (or even NOT harm your monitor/card)

Yeah, this is reasonable, however higher than 1600x1200 screen modes work just perfect in OS 3.9 and MorphOS...

Quote:

The problem with the second 1280 screenmode in prefs may be
because screenmode prefs just ignores a second mode which
has the same (or nearly the same) given details, happens
to me too


OK, I will remove this one and I'll try to push the sync in a better range to see if that fixes the problem of the 1280x1024x24 not showing...

Quote:

If you don't appliy 8, 16, 24 or 32 to the screenmode, the
system tries to create all of the possible modes.


Exactly, and it fails creating 1280x1024x24, setting the tooltype to: MODE=1280x1024@56
should create 1280x1024x8, 16 and 32 bit screenmodes, and it only creates 8 and 16 bit modes. This is not OK.


Cheers!

Dragster

Go to top



TopTop
(1) 2 »




Powered by XOOPS 2.0 © 2001-2016 The XOOPS Project