DT>How the hell am i meant to use extended registers with Turbo c++ v3.0 huh?
DT>it seems it doesnt know anything about the 386
You don't.  It doesn't know anything beyond the 286/287.
If you would actually bother to read the BASM.DOC, it clearly states it
doesn't know how to do 386 or 486 instructions.  (And it lists a few
other limitations.)
You can directly code the opcodes as inline assembly data bytes (as
opposed to inline asm instructions), but that's a pain, to put it
mildly.  By doing it as pure data bytes, you become the assembler and
are doing it in a form that BASM can handle.  (Be sure to use the
extended register prefix byte for the opcodes, otherwise, since the CPU
is still in 16 bit mode, you would still be working with 16 bit
registers.)
TC is designed for generic 16 bit 8086 code, rather than 386+ 32 bit
code.  And it is an old compiler.  When it was designed, 386's weren't
even dominant.  And a lot of people complained that it took at least a
286 to run....
--- QScan/PCB v1.19b / 01-0162
---------------