Welcome, Guest. Please login or register.

Recent Posts

Pages: 1 ... 6 7 [8] 9 10
71
Amiga Software Issues and Discussion / Re: Split Screen Hardware Scrolling
« Last post by RJRS on November 27, 2025, 11:37:13 PM »
I love that idea. Duel backgrounds that are not over layed but side by side, such a nice exploit. I guess independent hardware scrolling on each side but with a memory and colour depth hit - but worth it.
72
Amiga Marketplace / Re: Looking for a AmigaOne X5000
« Last post by SACC-guy on November 27, 2025, 10:46:05 PM »
where are you?

I may be able to help, but I really don't want to ship
73
Amiga/MorphOS/AROS Programmers Forum / Re: IDE for Amiga Basic
« Last post by SACC-guy on November 27, 2025, 10:45:03 PM »
how about True Basic?
74
Amiga Marketplace / Looking for a AmigaOne X5000
« Last post by AmigaBSD on November 27, 2025, 06:44:46 PM »
Hi, I am looking for an AmigaOne X5000. I would like to do some work to the PCIe driver. Would someone have a system they would be willing to sell me? Thanks!
75
Amiga/MorphOS/AROS Programmers Forum / Re: IDE for Amiga Basic
« Last post by ZXDunny on November 27, 2025, 06:04:08 PM »
BASinC is an IDE for Sinclair BASIC and that doesn't run on Windows either. BASinC is an emulator with ROM hooks to allow an IDE to operate on the in-memory BASIC code, run it, debug it, inspect variables etc etc.

I guess the OP wants something like that for AmigaBASIC.



I mean, I would have made a BASin for AmigaBASIC but... AmigaBASIC is bloody awful.
76
Amiga Emulation / Re: Minimig ITX / TF536 and attempting to use scsi.device on both
« Last post by F0LLETT on November 27, 2025, 02:01:28 PM »
No. The name "scsi.device" does say nothing about its function. The A4000T ROM has a scsi.device for IDE and another one for SCSI. There are many more expansions which use the name scsi.device for their drivers, but they are all for different hardwares. It is a convention that drivers which find the name scsi.device already in use rename themselves to 2nd.scsi.device, 3rd.scsi.device and so on. The same happens in the A4000T. If there are no IDE devices, the SCSI driver is called scsi.device. If there are no SCSI devices, the IDE driver is scsi.device. If both are present, IDE is scsi.device and SCSI is 2nd.scsi.device.

So just renaming would not work, as you would still need the driver to point to another address, else it would still conflict I'm guessing.
77
Amiga Emulation / Re: Minimig ITX / TF536 and attempting to use scsi.device on both
« Last post by Thomas on November 27, 2025, 01:09:52 PM »

No. The name "scsi.device" does say nothing about its function. The A4000T ROM has a scsi.device for IDE and another one for SCSI. There are many more expansions which use the name scsi.device for their drivers, but they are all for different hardwares. It is a convention that drivers which find the name scsi.device already in use rename themselves to 2nd.scsi.device, 3rd.scsi.device and so on. The same happens in the A4000T. If there are no IDE devices, the SCSI driver is called scsi.device. If there are no SCSI devices, the IDE driver is scsi.device. If both are present, IDE is scsi.device and SCSI is 2nd.scsi.device.
78
Amiga/MorphOS/AROS Programmers Forum / Re: IDE for Amiga Basic
« Last post by jj on November 27, 2025, 12:52:54 PM »
How can you have an IDE for Amiga Basic running on Windows?

Amiga Basic does not run on windows ?
79
Amiga Emulation / Re: Minimig ITX / TF536 and attempting to use scsi.device on both
« Last post by F0LLETT on November 27, 2025, 12:38:30 PM »
I am not a hardware expert but I believe in theory this should be possible. You would also have to make a 2nd.scsi.device which looks at the new address range. And you won't be able to boot from the TF IDE any more unless you hack a Kickstart ROM which contains both scsi.device drivers.

Could you use the 2nd.scsi.device from A4000T rom?
80
Amiga Emulation / Re: Minimig ITX / TF536 and attempting to use scsi.device on both
« Last post by Thomas on November 26, 2025, 02:07:36 PM »

I am not a hardware expert but I believe in theory this should be possible. You would also have to make a 2nd.scsi.device which looks at the new address range. And you won't be able to boot from the TF IDE any more unless you hack a Kickstart ROM which contains both scsi.device drivers.
Pages: 1 ... 6 7 [8] 9 10