Browsing this Thread:
1 Anonymous Users
|
Re: DClock 1.6
|
||||
|---|---|---|---|---|
|
Home away from home
 
|
Quote:
Yes. Just noticed a strange thing about PCITool... it doesn't save always the full info. The IRQ info was missing and every time that a device info is saved, the less information is saved to the log file.
Posted on: 2018/5/15 19:27
|
|||
|
||||
|
Re: DClock 1.6
|
||||
|---|---|---|---|---|
|
Home away from home
|
Quote:
It sounds like something failed compiling the native toolchain, though I would need more information to determine what?s wrong, and just now I can?t really look into it. Quote:
It would need the sdk atleast which isn?t yet worked on for ABI v1
Posted on: 2018/5/14 21:10
|
|||
|
||||
|
||||
|
Re: DClock 1.6
|
||||
|---|---|---|---|---|
|
Home away from home
|
Quote:
I assume the nvidia one is the one displaying incorrectly? Quote:
Posted on: 2018/5/14 20:54
|
|||
|
|
||||
|
||||
|
Re: DClock 1.6
|
||||
|---|---|---|---|---|
|
Home away from home
|
Tring to compile running native avi v1 i386 I get this problem.
/RAM Disk/U/DClock> gcc Draw.c Main.c SetAlarm.c Window.c /Developer/lib/gcc/i386-aros/4.6.4/libgcc.a: file not recognized: File format not recognized Kalamtee: I understand with your makefile I need to compile from the source tree. What do I need to change to compile from native? I get this. 7.Work:AROS-20180513-source> make local-dclock make: *** No rule to make target `local-dclock'. Stop. I also tried this: 7.Work:AROS-20180513-source/tools/DClock> edit mmakefile.src Here I removed aros.config in the include as the compiler did not find it. 7.Work:AROS-20180513-source/tools/DClock> make -f mmakefile.src mmakefile.src:17: *** missing separator. Stop. 7.Work:AROS-20180513-source/tools/DClock>
Posted on: 2018/5/13 21:13
Edited by nikolaos on 2018/5/13 22:39:31
Edited by nikolaos on 2018/5/14 19:43:41 Edited by nikolaos on 2018/5/14 19:51:44 |
|||
|
www.aspireos.com
|
||||
|
||||
|
Re: DClock 1.6
|
||||
|---|---|---|---|---|
|
Home away from home
|
@Kalamatee
No, my main pc has an Nvidia graphic card and the other has an Intel GMA integrated one. Driver Name: PCINative Direct bus: yes I?? base: 0x0000000 Hardware info: IA32 native direct access PCI driver Description: Video PC Compatible VGA Vendor name: NVIDIA Corporation Product name: GT218 [GeForce 210] Subsystem: Micro-Star International Co., Ltd. [MSI] : N210 [Geforce 210] PCIe graphics adapter Used by: VendorID: 0x10de ProductID: 0x0a65 RevisionID: 0xa2 Class: 0x03 Subclass: 0x00 Interface: 0x00 ROM Base: 0xfea00000 ROM Size: IRQ: Status: IO: no, MEM: yes, Master: yes, PaletteSnoop: no, 66MHz capable: no RangeList_0: Bar0: Memory at 0xfd000000 (size 0x1000000) RangeList_1: Bar1: Prefetchable Memory at 0xd0000000 (size 0x10000000) RangeList_2: Bar2: Memory at 0xfebff000 (size 0x1000) RangeList_3: Bar3: Prefetchable Memory at 0xce000000 (size 0x2000000) RangeList_4: Bar4: Prefetchable Memory at 0xfbff0000 (size 0x10000) RangeList_5: Bar5: I/O at 0xdc00 (size 0x80) Driver Name: PCINative Direct bus: yes I?? base: 0x0000000 Hardware info: IA32 native direct access PCI driver Description: Video PC Compatible VGA Vendor name: Intel Corporation Product name: 82945G/GZ Integrated Graphics Controller Subsystem: Gigabyte Technology Co., Ltd : GA-EG45M-DS2H Mainboard Used by: IntelGMA VendorID: 0x8086 ProductID: 0x2772 RevisionID: 0x02 Class: 0x03 Subclass: 0x00 Interface: 0x00 ROM Base: N/A ROM Size: N/A IRQ: 5 (A) Status: IO: yes, MEM: yes, Master: yes, PaletteSnoop: no, 66MHz capable: no RangeList_0: Bar0: Memory at 0xe2000000 (size 0x80000) RangeList_1: Bar1: I/O at 0xc000 (size 0x8) RangeList_2: Bar2: Prefetchable Memory at 0xd0000000 (size 0x10000000) RangeList_3: Bar3: Memory at 0xe2080000 (size 0x40000) RangeList_4: Bar4: I/O at 0xb000 (size 0x20) RangeList_5: IO ranges from a000 to a000
Posted on: 2018/5/12 8:09
|
|||
|
||||
|
Re: DClock 1.6
|
||||
|---|---|---|---|---|
|
Home away from home
|
hmm, on m68k it works perfectly..
needed to add retun at the end of main function though.. funny stuff.
Posted on: 2018/5/11 19:36
|
|||
|
||||
|
Re: DClock 1.6
|
||||
|---|---|---|---|---|
|
Home away from home
|
isnt that pretty crashy? like when moving the window around the screen:
################################################################################
i have added few casts and such in Main.c to make it compile for abiv1. attached. paolo, you could test if it works for abiv0. but perhaps something more needs to be undertaken. Attach file: Link only for registered users
Posted on: 2018/5/11 19:15
|
|||
|
||||
|
Re: DClock 1.6
|
||||
|---|---|---|---|---|
|
Home away from home
|
Quote:
Do they both use the same gfx driver?
Posted on: 2018/5/11 4:15
|
|||
|
|
||||
|
||||
|
Re: DClock 1.6
|
||||
|---|---|---|---|---|
|
Home away from home
|
I really don't understand what's happening. Just tried DClock on a different pc with both IcAROS 2.1.1 and 2.2.1 and there DClock works just fine. What's wrong?
Posted on: 2018/5/10 21:10
|
|||
|
||||
|
Re: DClock 1.6
|
||||
|---|---|---|---|---|
|
Home away from home
|
On my IcarOS 2.2 I do not know any difference
Attach file:  (0.00 KB)
Posted on: 2018/5/9 22:50
|
|||
|
||||
You can view topic.
You cannot start a new topic.
You cannot reply to posts.
You cannot edit your posts.
You cannot delete your posts.
You cannot add new polls.
You cannot vote in polls.
You cannot attach files to posts.
You cannot post without approval.
You cannot use topic type.
You cannot use HTML syntax.
You cannot use signature.
You cannot create PDF files.
You cannot get print page.
