Login
Username:

Password:

Remember me



Lost Password?

Register now!

Sections

Who's Online
127 user(s) are online (81 user(s) are browsing Forums)

Members: 3
Guests: 124

kas1e, joerg, LiveForIt, more...

Headlines

Forum Index


Board index » All Posts (Deniil)




Re: I call out for all you porting gurus
Quite a regular
Quite a regular


@afxgroup

Oh my god it worked! The whole program compiled

Well, almost, I got some linker errors about unix owner something. Think I can get around that..

Thankyou!

Btw. Do you happen to know if the ANSI file functions support 64-bit when using g++ straight off on OS4, or do I need to rewrite all that into OS4 dos.library??
No problem, just wondering...

@spotUp

That's a secret ;)
No it's unrar and my aim is 64-bit ability to be able to extract huge rar archives usually divided into 50MB chunks.

Perhaps it's already done in the existing port though without it being mentioned.... don't know..

Software developer for Amiga OS3 and OS4.
Develops for OnyxSoft and the Amiga using E and C and occasionally C++
Go to top


I call out for all you porting gurus
Quite a regular
Quite a regular


Hi!

I'm about to port my first Linux tool to Amiga (using OS4 and the public SDK), but the first error is this:
"error: sys/file.h: No such file or directory"

Simple, eh?
This file must be used by numeros ported tools, so what do I need to install etc. to not run into a million similar "easy" setbacks?

You porting gurus must know!

Software developer for Amiga OS3 and OS4.
Develops for OnyxSoft and the Amiga using E and C and occasionally C++
Go to top


Re: Any hope for DVI out support in OS4?
Quite a regular
Quite a regular


@LiveForIt

Quote:

What does suck, is programs that crash your computer like AmiIRC.


I noticed that changing the MUI layout of AmIRC from smart to simple refresh stopped it crashing. I never have crashes with AmIRC on OS4, but I only use its arexx port for small commands like changing nick...

@ssolie

Quote:

ssolie wrote:
@TMTisFree
Quote:
...Second it does not crash, it throws DSI error and works fine after ignoring it.


That is not correct. What you have done it put the application into an indeterminate state. Since AmigaOS is not a memory protected operating system you have also put your entire system into an indeterminate state. The DSI means the program is broken. The "Ignore" button is not a feature to make broken programs suddenly work fine. We should all be clear on this.


That depends on the DSI, if it is a read or a write, and what the program did with the incomplete read or write it perfromed.

Some programs completely lock up the system when Continued, or especially when Ignored, but some just continue fine.

Consider this:
call func(NULL);
int func(arg) {
if(arg[0] && arg) { //incorrect if-statment causes harmless DSI
return do_something(arg);
}
return 0;
}


BTW.
For which gfx cards is DVI supported?? Radeon 9250?

Software developer for Amiga OS3 and OS4.
Develops for OnyxSoft and the Amiga using E and C and occasionally C++
Go to top


Re: Any hope for DVI out support in OS4?
Quite a regular
Quite a regular


@Rogue

Quote:

It's true. DVI support will be in the next update.


Great!!

So the next obvious question from me is this:
Can we use dual screens/monitors on dual-head gfx-cards?? I mean like Workbench on DVI and DirOpus on VGA?? Please....

Having one screen extended onto two monitors is not something I ever expect Amiga to have, but having each output on a gfx card represent a screen of its own is a concept the OS already has, it should only be a matter of the drivers, right?

Having two or more gfx cards in an Amiga displaying two screens at the same time is already possible, just not on the A1 because of the current drivers as I understand.

Software developer for Amiga OS3 and OS4.
Develops for OnyxSoft and the Amiga using E and C and occasionally C++
Go to top


Re: Problem trying to run OWB
Quite a regular
Quite a regular


@joerg

Quote:

It's similar to the problems Raziel has, it's executing random code instead of the correct function but in your case there aren't even any shared objects involved, the function it should have called is in the OWB executable itself. No idea why it doesn't work for 3 or 4 users


Just as an update:
I just changed my Vcore from 1.59V to 1.64V on my G4 7455 (933MHz 1.85V version, running at 866MHz) and now OWB 1.24 starts every time!!

Quote:

But the python crashlog makes no sense at all, c:python is a tiny executable with only about 1.6 KB code which just calls functions in libpython25.so but in your crashlog are offsets of over 1.1 MB from the start of the python executable!?


Now I get zero-page exceptions everytime I try to start python:

[Edit: Please do not post crash logs in the forum. Post them at http://crashlog.os4depot.net and then post a link to it here on amigans]


Edited by orgin on 2008/5/17 16:20:38
Software developer for Amiga OS3 and OS4.
Develops for OnyxSoft and the Amiga using E and C and occasionally C++
Go to top


Re: Problem trying to run OWB
Quite a regular
Quite a regular


@joerg

I should note that all my SOs have the exact same md5sum as those of ZeroG (see the news on AW.net). I have all in SObjs: and none in the OWB dir. Perhaps we can rule out the SOs and go on to the toolbar images and fonts needed?? Something I should know??

I noticed that OWB v1.2x does not include the toolbar images, but I still have them in my OWB dir!

Python crashed with a DSI when I just executed "python" in a shell in ram: with the assign set.

It's a newlib crash. Do I need a newer OS4 beta newlib? It requires v3.9 but I have v52.33..?

Quote:

Crash log for task "python"
Generated by GrimReaper 52.3
Crash occured in module newlib.library.kmod at address 0x016032B8
Type of crash: DSI (Data Storage Interrupt) exception

Register dump:
GPR (General Purpose Registers):
0: 63308261 6148ABC0 4BFF85F9 63308261 00000000 6FFAA000 7DB90E8C 00000001
8: 69FED064 00000000 00A00000 63308261 48612048 62ECDD60 00000000 00000000
16: 7DAD80D0 7DAD8020 7DAD8600 00000003 00000000 68A41280 00000000 00000001
24: 01C0F35C 00000018 01C92810 65A02800 63308248 63308248 7DB90D50 6148ABD0


FPR (Floating Point Registers, NaN = Not a Number):
0: nan 0 0 0
4: 0 0 0 0
8: 0 0 0 0
12: 1.45833 68.5417 0 0
16: 0 0 0 0
20: 0 0 0 0
24: 0 0 0 0
28: 0 0 0 0

FPSCR (Floating Point Status and Control Register): 0x82024000


SPRs (Special Purpose Registers):
Machine State (msr) : 0x0000F030
Condition (cr) : 0x48612048
Instruction Pointer (ip) : 0x016032B8
Xtended Exception (xer) : 0x20000005
Count (ctr) : 0x01603248
Link (lr) : 0x7DC45880
DSI Status (dsisr) : 0x40000000
Data Address (dar) : 0x00000000



680x0 emulated registers:
DATA: 015DCF48 00000000 00000000 00000000 00000000 00000000 00000000 00000000
ADDR: 6148DF58 008F2AD7 015DCF48 00000000 00000000 00000000 6FF901AC 6148DD98
FPU0: 0 0 0 0
FPU4: 0 0 0 0



Symbol info:
Instruction pointer 0x016032B8 belongs to module "newlib.library.kmod" (HUNK/Kickstart)

Stack trace:
native kernel module newlib.library.kmod+0x000288f8
module python at 0x7DB90E8C (section 5 @ 0xB8E6C)
native kernel module kernel+0x0003b468
native kernel module dos.library.kmod+0x0001a7f8
native kernel module dos.library.kmod+0x0001ae2c
module python at 0x7DB90F9C (section 5 @ 0xB8F7C)
module python at 0x7DB91064 (section 5 @ 0xB9044)
module python at 0x7DB93D00 (section 5 @ 0xBBCE0)
module python at 0x7DB78228 (section 5 @ 0xA0208)
module python at 0x7DB77F68 (section 5 @ 0x9FF48)
module python at 0x7DB79980 (section 5 @ 0xA1960)
module python at 0x7DB78FE4 (section 5 @ 0xA0FC4)
module python at 0x7DB7889C (section 5 @ 0xA087C)
module python at 0x7DB78B2C (section 5 @ 0xA0B0C)
module python at 0x7DB428E0 (section 5 @ 0x6A8C0)
module python at 0x7DC070B8 (section 5 @ 0x12F098)
module python at 0x7DAE2FF4 (section 5 @ 0xAFD4)
module python at 0x7DB54C74 (section 5 @ 0x7CC54)
module python at 0x7DB50890 (section 5 @ 0x78870)
module python at 0x7DB52D34 (section 5 @ 0x7AD14)
module python at 0x7DB4C074 (section 5 @ 0x74054)
module python at 0x7DB75FF0 (section 5 @ 0x9DFD0)
module python at 0x7DB76910 (section 5 @ 0x9E8F0)
module python at 0x7DB77EEC (section 5 @ 0x9FECC)
module python at 0x7DB79980 (section 5 @ 0xA1960)
module python at 0x7DB78FE4 (section 5 @ 0xA0FC4)
module python at 0x7DB7889C (section 5 @ 0xA087C)
module python at 0x7DB78B2C (section 5 @ 0xA0B0C)
module python at 0x7DB428E0 (section 5 @ 0x6A8C0)
module python at 0x7DC070B8 (section 5 @ 0x12F098)
module python at 0x7DAE2FF4 (section 5 @ 0xAFD4)
module python at 0x7DB54C74 (section 5 @ 0x7CC54)
module python at 0x7DB50890 (section 5 @ 0x78870)
module python at 0x7DB52D34 (section 5 @ 0x7AD14)
module python at 0x7DB4C074 (section 5 @ 0x74054)
module python at 0x7DB75FF0 (section 5 @ 0x9DFD0)
module python at 0x7DB76910 (section 5 @ 0x9E8F0)
module python at 0x7DB77EEC (section 5 @ 0x9FECC)
module python at 0x7DB79980 (section 5 @ 0xA1960)
module python at 0x7DB78FE4 (section 5 @ 0xA0FC4)
module python at 0x7DB7889C (section 5 @ 0xA087C)
module python at 0x7DB78B2C (section 5 @ 0xA0B0C)
module python at 0x7DB428E0 (section 5 @ 0x6A8C0)
module python at 0x7DC070B8 (section 5 @ 0x12F098)
module python at 0x7DAE2FF4 (section 5 @ 0xAFD4)
module python at 0x7DAE3218 (section 5 @ 0xB1F8)
module python at 0x7DB7A0C4 (section 5 @ 0xA20A4)
module python at 0x7DB787B0 (section 5 @ 0xA0790)
module python at 0x7DB847A4 (section 5 @ 0xAC784)
module python at 0x7DB840D0 (section 5 @ 0xAC0B0)
module python at 0x7DB84134 (section 5 @ 0xAC114)
module python at 0x7DAD9250 (section 5 @ 0x1230)
module python at 0x7DAD86E0 (section 5 @ 0x6C0)
native kernel module newlib.library.kmod+0x00000de4
native kernel module newlib.library.kmod+0x00002348
native kernel module newlib.library.kmod+0x000026f4
module python at 0x7DAD813C (section 5 @ 0x11C)
native kernel module kernel+0x0003b468
native kernel module kernel+0x0003c528
native kernel module kernel+0x0004ef8c



PPC disassembly:
016032b0: 4182ffe4 beq+ 0x1603294
016032b4: 7d094378 mr r9,r8
*016032b8: 88090000 lbz r0,0(r9)
016032bc: 39290001 addi r9,r9,1
016032c0: 2f800000 cmpwi cr7,r0,0


The rest is probably as in my OS4depot log.

I did however not reboot after OWB crashed...

Software developer for Amiga OS3 and OS4.
Develops for OnyxSoft and the Amiga using E and C and occasionally C++
Go to top


Re: Problem trying to run OWB
Quite a regular
Quite a regular


@joerg

Hi!

Now I posted a crashlog at OS4depot:
ID 48

Software developer for Amiga OS3 and OS4.
Develops for OnyxSoft and the Amiga using E and C and occasionally C++
Go to top


Re: OWB (1.20/1.2) bugs and feature requests
Quite a regular
Quite a regular


@joerg

I have a 7455 delivered original with my A1-XE...

I will however up my Vcore one step since I think it is a little too low since I switched PSU to a better one.

Software developer for Amiga OS3 and OS4.
Develops for OnyxSoft and the Amiga using E and C and occasionally C++
Go to top


Re: Problem trying to run OWB
Quite a regular
Quite a regular


@joerg

Thankyou for answering!

I understand I break some other programs by removing the .sos, so I backed them up of course. Will reinstall only those three you mentioned and try again.

I'll post or upload a crashlog when I get home.

Software developer for Amiga OS3 and OS4.
Develops for OnyxSoft and the Amiga using E and C and occasionally C++
Go to top


Re: OWB (1.20/1.2) bugs and feature requests
Quite a regular
Quite a regular


@Valiant

Quote:

Valiant wrote:
@Raziel

1.20 still immediately GR's upon startup here.


Same for me, but with v1.21 and 1.24.

I have used 1.15 and 1.19 successfully before but I can't get these new versions to run. I keep getting ISIs at startup of OWB. Sometimes after the window has opened and drawn its nav bar, but often before any window is opened.

Can someone list everything needed to make it run successfully? I have installed the Cyberbit font and all *.sos (into SObjs:) from v1.21 and v1.24 but it just crashes. Is there anything else I need to do?? I have not downloaded and installed all version throughout time. Can I have missed an .so that is not included now anymore??

There must be something wrong with my install but I can't figure out what

Software developer for Amiga OS3 and OS4.
Develops for OnyxSoft and the Amiga using E and C and occasionally C++
Go to top


Re: Problem trying to run OWB
Quite a regular
Quite a regular


@joerg

I also have a problem getting OWB to start, but for me it just crashes with an ISI 80% of the times I try to start it.

I tried removing all .so files and installing the .so from OWB 1.21 and 1.24 but apparently more are lacking. Probably some from OS4 July, right?

But I used to have these, and I have the Cyberbit.ttf installed with typemanager. It still gives me an ISI (almost) everytime I try to start it and Snoopy doesn't report anything at all. I have removed cookies.

I start from the icon (WB) which is the original icon with 512k stack and no tooltypes changed.

Please help?

I have had it running, and the last time the ISI came after the window had opened. I seem to recall that the ISI is somewhere in the zero page. Those times I don't got an ISI at startup OWB run fine until I closed it.

Software developer for Amiga OS3 and OS4.
Develops for OnyxSoft and the Amiga using E and C and occasionally C++
Go to top



TopTop
« 1 ... 24 25 26 (27)




Powered by XOOPS 2.0 © 2001-2023 The XOOPS Project