Good thing I got lucky and have USB storage alongside PTP and MTP options

I need to learn driver development anyway

the caller and callee are compiled separately along with some sections of the called routines replaced by code from other compilers

so all the entry points have to comply without any wrapper due to being direct accessible functions from outside callers

as it is the documentation for GCC in this case is a known incomplete section with regards to explaining the use of as within GCC

Quote:

unless you require dictating which register is what variable to keep consistency between compilers when needing to deal with such details

at that time you are completely on your own

I am yet to get any help clarifying just such a problem where "relying on the compilers intelligence" breaks the design due to inconsistent state

as I need 24 registers to retain state and not lose it by restoring the contents on function exit or pushing it onto the stack at entry

and this is for one of my existing projects

any suggestions? as I need to perform the above *inside* a C wrapper that is not a single function
｢at least 282 seperate entry points sharing this set of state ｣ and no it's not a design flaw

I would like to make it work on Amiga OS 4 and MorphOS if possible

Samba is the server package and windows can then use the Amiga as any other windows share

you will need to pm pay attention to the settings in smb.conf and the windows network security levels

smbclients also share the server package name so can make confusion

Do the .so files require any special handling for TimberWolf to run properly?

I'm still finding I can't run Python or TimberWolf at all... and I am wondering what I may be missing to rectify the fault (I am sure I am missing something as these are the only two programs with any issues)

anyway... I'm going to be checking to see if the Locale settings (I'm in Japan so I have to work on supporting Japanese encoding) have anything to do with it...

Does anyone have a complete archive of TuneNet latest with ALL the plugins pre-installed?

Or do I need to generally mirror the entire os4depot.net directory for TuneNet and work from that ?

I've been playing around with it and seen several crashes...

mostly do with with filenames with non-ASCII (UTF-8 or ISO-2022-JP) characters in the name and selecting to add a directory of media crashes the program...

Does anyone else get these behaviour?

I generally start with version 0.x for the initial skeleton materials, bumping to 1.x series when compilation produces something usable.

I then bump revisions based on how many milestones are passed.

If I were to do it based on changes alone then the count would be a seriously large revision number that would just be too ridiculous to release :)

but I do agree with the point about system sync being a waste of time (just document it already somewhere the users can get to easily!!!)

Bufallo Wireless Keyboard and Mouse sets (Japanese Wireless Keyboards with Mice)

These work with only a Keymap required (misses 4 keys from the layout I have made myself so far)

only | is currently not type-able natively on an AmigaOS 4.x machine... everything else on the keyboard works fine

Needs to have 3 more Japan only keys mapped to codes for raw input mapping

How about "tagging" threads with a list of tags on the site?

that way you can search by tag and not worry about anything else?

Just for completeness... known information is repeated here.

For the A1000 it uses an RJ11 connector for the keyboard,

For the A500/A500+ they use a MOS chip and header to the motherboard,

the A600 and A1200 have the Keyboard Controller itself directly on the motherboard

For the A2000 and A3000 the DIN A5? plug is used for the AT style keyboard connector

For the A4000 the Keyboard is PS/2 plug connected.

it will be possible to use a USB to PS/2 or USB to DIN adapter but it will need to be programmed for handling the Amiga scancodes off the keyboard

All of these have a 5v DC line for the power feed excepting the USB feed which is an AC type of power feed to my understanding...

If anything here is wrong, can you please correct me?

USB is defined as a Data over Power standard...

The electrical lines provide both power and signalling paths

If you have some kind of PS/2 connector on the X1000 then you may have a chance to hookup an Amiga Keyboard however the scancodes provided to the X1000 would not be understood using the default firmware and would require a new Keymap setup.

It may be better for you to simply buy another PC USB keyboard to replace the dell one once it becomes unusable.

I wonder if anyone will ever collect signatures from various Amiga OS developers...

I know my own scrawling would be more than... interesting... having *three* legal names kinda makes signing a chore.

I'd have to sign three names in two languages... and a specific way all on top of each other...

I just hope Kanji is not offensive to anyone?

Wow!... hopefully Aladdin4D got some development work from it

@Hans: well, marking the microcode for later when the 4xxx series is acceptably complete before the 5xxx series support properly starts is at least showing the functionality is roadmapped :)

I've got a 5450 and I'll definitely be waiting for when the drivers are happilly updated enough for you to start expanding to the newer cards

I'll be up for trying to work on the library as part of a team effort to see it at least completed.

I may end up needing to use this library for future work and all of your effort to date would still count as far as I am concerned.

You have done what you can and you are asking for someone else to take it further...like a relay race...I'm more than willing to do part of the leg work even if I don't see anything other than a finished product at the end.

@Antique: sorry to burst your bubble... I'm a New Zealander, and my first language is English.

However the rest of my family... is going to include Japanese heritage pretty darned soon anyway :P

@Elwood: *damm* would it not be easier to just make the one model with that present from the start? then the AOS4.x and Linux Kernels would have the option of a NAND FlashROM Boot disk I would think

ahh well... I will just have to fake it or pay extra?

anyway I will finish getting the 440 I will start building with first...get the money for the 460 then buy it

I would be more personally interested in an updated sam460ex style design with either more memory or an updated processor keeping the GPU entirely seperate from the CPU unless the GPU comes with other IO functions for being part of a chipset implementation.

other than that would there really be any point considering "desktop" equipment has to be of considerable usability vs just being an older mobile device

Where the Pi has cheap hardware it also comes at the cost of lower specifications.

sam460ex motherboard,
both Ethernet ports,
disabled SATA (using a PCI SATA card)
with NAND Flash of 512MB present

is this configuration possible and how much?

Shipping would be to Japan (Matsudo City, Chiba Prefecture)
just outside Tokyo.

PS. Tried using the AmigaKit site for estimating shipping...
It lets me estimate shipping either for US/CA or EU local only... when going International the shipping still appears as "local"...
Maybe I am missing something or messing up a setting?

Browsers used were Firefox and Chrome.

Well I would request that you ignore any special "library" mode and instead of that have an option to make a linkable object being output instead of an EXE.

That way if someone wants to write a library or the startup code themselves (such as myself) there is no limitation on doing such things as libraries and devices with AmigaE.

I would like to see PortablE able to stand on its own with compilation and linking able to be staged if required

I look forward to checking this out myself,

The only question I have is whether you will have any "library mode" for developing AmigaOS4.x or other platform libraries?
possibly just making object files able to be output and linked afterwards?

Curious as the original AmigaE by Wouter had a library mode and inherited a detail from SAS/C style startup code.