Image Map Image Map
Page 43 of 44 FirstFirst ... 33394041424344 LastLast
Results 421 to 430 of 438

Thread: XTIDE Universal BIOS

  1. #421
    Join Date
    Mar 2019
    Location
    Hamburg/Germany
    Posts
    4

    Default

    Quote Originally Posted by hwarin View Post
    [2 years and a reply !]

    ==> Thanks, WallyB - I definitely must have a try of this, I've let my A1000+BridgeBoard setup away since long as I did not find a solution to use XT-IDE with it.
    Hi,

    i don't think this is a real solution.
    The problem is that INT19-Init is never called with activated Janus-Handler, VERY_LATE_INIT (INT13) is called, but
    fails here (marked) in Int13hBiosInit.asm:
    Code:
    36	Int13hBiosInit_Handler:
    37	    ; Initialize XTIDE Universal BIOS only if Int13hBiosInit_Handler is still at
    38	    ; vector 13h. Otherwise some other BIOS has hooked us and our very late
    39	    ; initialization is not possible.
    40	    push    ds
    41	    push    ax
    42	    LOAD_BDA_SEGMENT_TO ds, ax
    43	    pop     ax
    44	    cmp     WORD [BIOS_DISK_INTERRUPT_13h*4], Int13hBiosInit_Handler
    45	    pop     ds
    46	    jne     SHORT .VeryLateInitFailed   ; XTIDE Universal BIOS does not work.  <<<<==== Fails here
    47	
    48	    ; Ignore all but read command (assumed to read boot sector)
    49	    cmp     ah, READ_SECTORS_INTO_MEMORY
    50	    je      SHORT Int19h_BootloaderHandler
    If you delete the >jne SHORT .VeryLateInitFailed< XTIDE starts with activated Janus-Handler and the HDD is accessible, but the Janus-functions AWRITE, AMOUSE,... doesnt work.
    I think a "boot-mode" of a Seagate ST01/02 (INT13?) should help, this controller works out of the box.

  2. #422

    Default

    Hi, Toms01

    I think that you're probably pointing the real issue. I've spent hours in the code years ago and did not seen that (not expecting much of VeryLateInit … and more focussed on INT19).

    ==> If try to translate from the code : "If Int13 was hooked by someone else, don't try to initialize the BIOS and fail", what's pretty clear, this someone might be Janus ...

    I don't know what you mean exactly with ST01/02 boot mode [ST01/02 seems to be SCSI boards] but I've got a Tandon TM9362 [including a WD1002 MFM board] fitted natively in the sidecar (*) and it works perfectly well (never tryed AWRITE/AMOUSE anyay). (*) It's so common that I have the exact same board in the M24.

    Thanks so much for pointing this, now, how can we go further ?
    [it should be possible to just patch actual code with NOPs in order to test ? I Don't have the tool chain ready for a custom compilation]

    Regards - Hervé
    Last edited by hwarin; March 27th, 2019 at 01:56 PM.

  3. #423
    Join Date
    Aug 2015
    Location
    Borås, Sweden
    Posts
    29

    Default

    I'm having a problem with XT-IDE serial port booting certain floppy image sizes only.

    My setup is IBM 5150 with an glitchworks v4 XT-ide card, running XT-IDE universal bios 2 beta 3 and also a 8-bit 16550 UART.

    The serial server is a notebook running win10x86 with a USB serial device. On this system I have multiple floppy image files.

    I can successfully boot disk images with 360kB or 1.44MB size, but not 720kB disk images. I have tried multiple image files with the same result, and I have also verified that the images är in fact bootable when mounted on bochs. The speed setting doesn't make any difference.

    Running serdrive with higher verbosity level reveals that sectors 0-8 are read, but not further, and I suspect this might be the issue.

    When starting serdrive with 720kB image it's identified as a CHS 80:1:18 device, when I guess it should be 80:2:9. The values are hard coded in source, and the parameters are set based on image file size.

    Has anyone else had this problem?

    Best regards,
    Måns

  4. #424

    Default

    Quote Originally Posted by mrmanse View Post
    When starting serdrive with 720kB image it's identified as a CHS 80:1:18 device, when I guess it should be 80:2:9. The values are hard coded in source, and the parameters are set based on image file size.
    That is indeed a bug! Thank you Måns, not only for reporting it but also for finding the cause. I can't believe no one has discovered this until now.

    This one should work;
    serdrive.zip
    Looking for a cache card for the "ICL ErgoPRO C4/66d V"

  5. #425
    Join Date
    Aug 2015
    Location
    Borås, Sweden
    Posts
    29

    Default

    Quote Originally Posted by Krille View Post
    This one should work;
    serdrive.zip
    Fantastic - thanks a lot!

    Can't wait to give it a try when I get off work.

    /Måns

  6. #426
    Join Date
    Aug 2015
    Location
    Borås, Sweden
    Posts
    29

    Default

    Quote Originally Posted by Krille View Post
    This one should work;
    serdrive.zip
    Indeed it does, very well. Thank you!

    /Måns

  7. #427

    Default

    Hi,

    I Don't know if I shall post in this thread or in "XTIDE Universal BIOS v2.0.0 beta testing" thread - I'm still facing an issue with last R601 version (and any known previous version) of IDE_XT BIOS. This seems to be a known issue in Amiga Community. (https://www.a1k.org/forum/showthread...t=xtide&page=4)

    The issue is with Commodore JANUS board [this board makes the link between an Amiga computer and the PC-XT "co-computer" that was optionally available by Commodore at the time Under the names of SideCar or BridgeBoard].

    In details, IDE_XT BIOS operates basically from "PC side" only when compilled with VeryLateInit option and with "jne SHORT .VeryLateInitFailed ; XTIDE Universal BIOS does not work." commented out.

    In facts, when it operates, IDE_XT disables completely JANUS operation.

    As a consequence, I've started to prepare a "VeryEarlyInit" option for IDE_XT, with my very limited coding capabilities, done in a similar way that what was doing regular WD controllers of the time. It seems to work, as JANUS BIOS now initializes after IDE_XT. The issue is that now, JANUS cycles 4 times in it's initialization then hangs the PC-side, as per screen shot. I've attached my binary and 3 versions of JANUS BIOS (I'm using currently v2.63).

    ==> Needing help to fix this problem as I Don't have any idea of what, in IDE_XT "VeryEarlyInit", may prevent JANUS to start correctly and I Don't see where or how to start for debugging
    ==> Keeping my current code and my reference Workbench at disposition of anyone interested in helping (too big to attach here in the forum)
    ==> Available also in any way to explain/test the issue

    r601_WithVeryEarlyInit_190421_minimal options.jpg

    Regards - Hervé
    Attached Files Attached Files

  8. #428
    Join Date
    Mar 2019
    Location
    Hamburg/Germany
    Posts
    4

    Default

    Hi Hervé, do you have actual sources about the "veryearlyinit"? I can do some tests
    toms01

  9. #429
    Join Date
    Nov 2017
    Location
    Manalapan, NJ
    Posts
    19

    Default

    Hello everyone.
    My friend and I are working on restoring a rare Soviet XT clone (based on 8086). This machine has an integrated IDE controller and an EGA card, but unfortunately, the BIOS from this board has been lost. We have already found compatible main bios and EGA videobios, now we are trying to revive the built-in IDE interface with the XT-IDE bios, but so far no luck. I have full schematics for this PC. Can anybody give advice, what setting should I try with XT-IDE? Thanks a lot.



  10. #430

    Default

    Hi, Filin

    I've not been able to view correctly your schematics, so, speaking in the Wind ...

    I'm a bit surprised that this "Soviet XT" had an IDE built-in interface. Would it be an XTA style interface (see WD140 or WD150 controllers) requiring special and rare and unreliable 8bits HDD ?
    ==> Possibly as it seems sufficiently modern and luxious to have an EGA board


    At first idea, I would try to disable any hardware regarding this interface and would plug directly a CF-IDE in an available slot

    Regards - Hervé

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •