Announcement

Collapse

Forum Rules and Etiquette

Our mission ...

This forum is part of our mission to promote the preservation of vintage computers through education and outreach. (In real life we also run events and have a museum.) We encourage you to join us, participate, share your knowledge, and enjoy.

This forum has been around in this format for over 15 years. These rules and guidelines help us maintain a healthy and active community, and we moderate the forum to keep things on track. Please familiarize yourself with these rules and guidelines.


Rule 1: Remain civil and respectful

There are several hundred people who actively participate here. People come from all different backgrounds and will have different ways of seeing things. You will not agree with everything you read here. Back-and-forth discussions are fine but do not cross the line into rude or disrespectful behavior.

Conduct yourself as you would at any other place where people come together in person to discuss their hobby. If you wouldn't say something to somebody in person, then you probably should not be writing it here.

This should be obvious but, just in case: profanity, threats, slurs against any group (sexual, racial, gender, etc.) will not be tolerated.


Rule 2: Stay close to the original topic being discussed
  • If you are starting a new thread choose a reasonable sub-forum to start your thread. (If you choose incorrectly don't worry, we can fix that.)
  • If you are responding to a thread, stay on topic - the original poster was trying to achieve something. You can always start a new thread instead of potentially "hijacking" an existing thread.



Rule 3: Contribute something meaningful

To put things in engineering terms, we value a high signal to noise ratio. Coming here should not be a waste of time.
  • This is not a chat room. If you are taking less than 30 seconds to make a post then you are probably doing something wrong. A post should be on topic, clear, and contribute something meaningful to the discussion. If people read your posts and feel that their time as been wasted, they will stop reading your posts. Worse yet, they will stop visiting and we'll lose their experience and contributions.
  • Do not bump threads.
  • Do not "necro-post" unless you are following up to a specific person on a specific thread. And even then, that person may have moved on. Just start a new thread for your related topic.
  • Use the Private Message system for posts that are targeted at a specific person.


Rule 4: "PM Sent!" messages (or, how to use the Private Message system)

This forum has a private message feature that we want people to use for messages that are not of general interest to other members.

In short, if you are going to reply to a thread and that reply is targeted to a specific individual and not of interest to anybody else (either now or in the future) then send a private message instead.

Here are some obvious examples of when you should not reply to a thread and use the PM system instead:
  • "PM Sent!": Do not tell the rest of us that you sent a PM ... the forum software will tell the other person that they have a PM waiting.
  • "How much is shipping to ....": This is a very specific and directed question that is not of interest to anybody else.


Why do we have this policy? Sending a "PM Sent!" type message basically wastes everybody else's time by making them having to scroll past a post in a thread that looks to be updated, when the update is not meaningful. And the person you are sending the PM to will be notified by the forum software that they have a message waiting for them. Look up at the top near the right edge where it says 'Notifications' ... if you have a PM waiting, it will tell you there.

Rule 5: Copyright and other legal issues

We are here to discuss vintage computing, so discussing software, books, and other intellectual property that is on-topic is fine. We don't want people using these forums to discuss or enable copyright violations or other things that are against the law; whether you agree with the law or not is irrelevant. Do not use our resources for something that is legally or morally questionable.

Our discussions here generally fall under "fair use." Telling people how to pirate a software title is an example of something that is not allowable here.


Reporting problematic posts

If you see spam, a wildly off-topic post, or something abusive or illegal please report the thread by clicking on the "Report Post" icon. (It looks like an exclamation point in a triangle and it is available under every post.) This send a notification to all of the moderators, so somebody will see it and deal with it.

If you are unsure you may consider sending a private message to a moderator instead.


New user moderation

New users are directly moderated so that we can weed spammers out early. This means that for your first 10 posts you will have some delay before they are seen. We understand this can be disruptive to the flow of conversation and we try to keep up with our new user moderation duties to avoid undue inconvenience. Please do not make duplicate posts, extra posts to bump your post count, or ask the moderators to expedite this process; 10 moderated posts will go by quickly.

New users also have a smaller personal message inbox limit and are rate limited when sending PMs to other users.


Other suggestions
  • Use Google, books, or other definitive sources. There is a lot of information out there.
  • Don't make people guess at what you are trying to say; we are not mind readers. Be clear and concise.
  • Spelling and grammar are not rated, but they do make a post easier to read.
See more
See less

XTIDE Universal BIOS v2.0.0 beta testing thread

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • modem7
    replied
    Originally posted by jerryt74332 View Post
    I also see that Real Time CLock could be on interrupt 2,4,5, or 7. as i type this i realize I dont know what it is set to, if it is on 5, could this be the problem?
    No. The RTC chip only generates an interrupt when its 'alarm' functionality is activated. 'Alarm' functionality is normally not active.

    Originally posted by jerryt74332 View Post
    Does the xt-ide need interrupt 5?
    No.

    Originally posted by jerryt74332 View Post
    Tonight I will try to disable the RTC and make sure it is not on 5 to trouble shoot the issue.
    Yes, because this could be an 'I/O port' (not interrupt) conflict between the XT-IDE card and the RTC.

    Leave a comment:


  • jerryt74332
    replied
    ISSUE: I have a XT-IDE Deluxe board with CF card on board that will not recognize any cf card, but only in one of my computers. It works great on 4 other motherboards.

    DETAILS: The computer I am trying to make work is a Leading Edge Technology 2010E, 8088 cpu 4.77 mhz XT 256k ram, motherboard has onboard CGA/MGA, Serial , parallel, time clock, and floppy controller. The XT-IDE Bios splash screen comes up, but it always says no drives found. error 1h! then boots from floppy fine. I have tried with onboard video, and with a VGA card and onboard disabled with same results. After booting from floppy id does not see any HDD with FDISK, There is no hard drive/MFM controller in system.

    If it helps the onboard stuffs is set as follows.

    Floppy drives: 1

    I also see that Real Time CLock could be on interrupt 2,4,5, or 7. as i type this i realize I dont know what it is set to, if it is on 5, could this be the problem?

    Does the xt-ide need interrupt 5? it is listed as "HARD DISK (PC/XT type computer only)"
    Tonight I will try to disable the RTC and make sure it is not on 5 to trouble shoot the issue.

    I will update this when I check system tonight.
    I am hoping someone will read this and just know. If not it will be hear for the next time.

    -Jerry




    mother board info
    https://stason.org/TULARC/pc/motherb...EVISION-1.html

    Leave a comment:


  • ajacocks
    replied
    It looks like the https://www.xtideuniversalbios.org site is down. Where is the current development being done? Obviously, code.google.com is in archive-only mode.

    - Alex

    Leave a comment:


  • NCommander
    replied
    Originally posted by Krille View Post

    This is interesting - a driver for the XT-IDE cards? Which cards exactly? All of them?

    Are you saying that interrupt vectors C0h to C3h are being overwritten? XUB doesn't use those interrupts so it must be something else causing this problem.
    So, VENIX's stock driver assumes a IBM Fixed Disk Controller, and tries to do DMA with it. I replaced it with an int 13h based driver which seems to work (albiet slowly, since VENIX only requests sectors 1 at a time). I need to get a memory watch kit setup to figure out exactly what's going on, but here's what I know:

    On startup, VENIX overrides the entire IVT with one of it's own design. It retains a few vectors (specifically, those listed in the IBM PC Technical References), and then replaces them all with a handler that prints the message "Unknown Interrupt (ignored).

    If the XT-IDE Universal BIOS is installed, VENIX prints out two unknown interrupt messages, and then crashes. I think this is a state machine falling apart, but I haven't quite worked out what's going on due to debugging difficulties. If the IVT at C0->C3 is retained with the values from start up, the system boots successfully. All four words MUST be retained. I can reproduce this crash and fix on multiple machines and in emulation.

    I need to setup Bochs or another emulator w/ a debugger so I can see what exactly is happening. I suspect something is accidently reading/writing those addresses since I looked through the code for any references and couldn't' find any.

    (I'm sorry for the slow responses, my account is low post count, so my posts have to be mod validated, and I don't get email notifications for replies it seems).

    Leave a comment:


  • Krille
    replied
    Originally posted by NCommander View Post
    Had something of a weird issue. Been working on writing a driver to get VENIX/86 working with the XT-IDE. VENIX, on startup, clobbers the ISVS and resets them with their own hooks. What I found is on floppy access, with the XT-IDE BIOS installed, if interrupted 0xC0 to 0xC3 are overridden, Venix gets several Unknown Interrupts, and dies. I looked at the XT-IDE source code, but I can't see any place where these ISVs are used. This seems to happen on latest nightly builds so I find myself rather confused on what's going on ...
    This is interesting - a driver for the XT-IDE cards? Which cards exactly? All of them?

    Are you saying that interrupt vectors C0h to C3h are being overwritten? XUB doesn't use those interrupts so it must be something else causing this problem.

    Leave a comment:


  • NCommander
    replied
    Had something of a weird issue. Been working on writing a driver to get VENIX/86 working with the XT-IDE. VENIX, on startup, clobbers the ISVS and resets them with their own hooks. What I found is on floppy access, with the XT-IDE BIOS installed, if interrupted 0xC0 to 0xC3 are overridden, Venix gets several Unknown Interrupts, and dies. I looked at the XT-IDE source code, but I can't see any place where these ISVs are used. This seems to happen on latest nightly builds so I find myself rather confused on what's going on ...

    Leave a comment:


  • Malc
    replied
    All my MFM drives that came with my IBM's are long dead, I do have one Japanese model that works and tried it in an XT with XUB and CF for a while, It worked fine but that was a long time ago. I use CF / SD / IDE Spinning rust or USB these days.

    Leave a comment:


  • Krille
    replied
    It should affect hard drives as well as floppy drives. I guess not that many people are using XUB with other hard drive controller BIOSes. Thinking back, the only bug reports I can remember mentioning XUB having problems coexisting with other hard drive controllers are the ones from people trying to use MFM controllers. alecv was (the?) one IIRC. It's also possible we've missed bug reports of course.

    Leave a comment:


  • Malc
    replied
    Originally posted by Krille View Post
    ..... or even other harddrive controllers together with XUB; this should now be fixed.
    I can't say i've had this problem but then i only have the XUB running on my IBM's these days and don't use MODULE_SERIAL_FLOPPY, Just curious, Does this just affect Floppy operations or does it also affect hard drive's as well on some systems ?.


    Leave a comment:


  • Krille
    replied
    r618 is out!

    pikadroo, freds and anyone else who has had problems using floppy drives or even other harddrive controllers together with XUB; this should now be fixed.

    Originally posted by pikadroo View Post
    I can't seem to find any mention of a problem I am having with floppy drives, so here it is maybe someone can help.

    With the XTIDE bios installed I am unable to format floppies due to a "Invalid media or Track 0 bad - disk unusable" error. My system is probably an extremely rare Cumulus brand 386SX with a built in phoenix bios that has limited IDE support. All version of the XTIDE bios in v2 will boot a CF card just fine into DOS 6.22 on this computer, it works so great I can't even believe it. The floppy format problem only occurs in v2 beta 2 and v2 beta 3 however, I can format floppies when I use v2 beta 1 just fine. If the XTIDE bios is removed from the computer formatting floppies works just fine.

    Thanks!
    -Drew
    Originally posted by freds View Post
    Hello,

    I am unable to have my 5.25 1.2M floppy drive properly recognized with ide_xt and ide_xtp. The drive is considered by the OS as a 360K one when such a bios is present. The drive works fine with ide_tiny, but then, no CF.

    My setup is:
    - PC Epson Equity II (NEC V30, 640 KB RAM, one 5.25 HD floppy, no extension board)
    - XT-CF Lite V4.1 (Address C800h, port 320h)
    - MS-DOS 6.2
    - Transcend CompactFlash Industrial CF300 128MB (TS128MCF300)
    - XTIDE bios r602 and previous (r528 customized from Sergey, r588...)

    Tests performed, without success:
    - Many changes of address and port on the XT-CF-Lite card, flashing both ide_xt and ide_xtp accordingly to port after running auto-configure in xtidecfg.
    - Build r602 on Linux with minimum DEFINES_COMMON in the makefile (progressively down to the options of DEFINES_XT_TINY). The floppy drive doesn't work as soon as MODULE_8BIT_IDE_ADVANCED is included, which is mandatory for CF support.

    When the drive is wrongly recognized, the same error as Drew noticed in #528 appears (unable to format the floppy).
    The functions 08h and 15h of int13 seem to be involved in floppy drives detection, so I tried calling them with debug utility. I'm not sure whether these functions are the only ones.

    Code I used for calling function 15h:

    xor ax, ax
    mov es, ax
    mov di, ax
    mov ah, 15
    mov dl, 00
    int 13
    int 3


    Function 15h result with drive recognized as HD (ide_tiny in ROM or ROM disabled):
    AX=0200 BX=0000 CX=0000 DX=0000 SP=FFEE BP=0000 SI=0000 DI=0000
    DS=16AD ES=16AD SS=16AD CS=16AD IP=0108 NV UP EI PL NZ NA PE NC

    Result with ide_xt or ide_xtp in ROM:
    AX=0200 BX=0000 CX=0000 DX=0000 SP=FFEE BP=0000 SI=0000 DI=0000
    DS=166E ES=166E SS=166E CS=166E IP=0109 NV UP EI NG NZ AC PE CY

    3 flags are different. I understand that the carry flag here means an error occurred in the function call.

    Function 08h with drive recognized as HD:
    AX=0140 BX=0000 CX=0000 DX=0000 SP=FFEE BP=0000 SI=0000 DI=0000
    DS=16AD ES=16AD SS=16AD CS=16AD IP=0108 NV UP EI NG NZ AC PO CY

    Function 08h with drive recognized as 360K:
    AX=0100 BX=0000 CX=0000 DX=0000 SP=FFEE BP=0000 SI=0000 DI=0000
    DS=166E ES=166E SS=166E CS=166E IP=0108 NV UP EI NG NZ AC PO CY


    AX contains 0140 when the drive is fine, 0100 when ide_xt or ide_xtp is in the ROM.

    Thanks for your help!
    Freddy

    Leave a comment:


  • jcarvalho
    replied
    Hello! I have an odd problem. I flashed an 27c with 16kb with the build r607 of xt_ide_386 after configure it with the provided software. I am using an 386DX40 with 8Mb of RAM and an CF with 8gb. All work very well, super happy. The problem is when I swap the graphic card for an ET4000 isa 16bit, I cant boot, the computer freezes on showing the first letters on screen with card info.
    When I remove the NIC with xt_ide, all is working. Using a 8900c gfx or an OAK card also good. But I would like to use my TSENG on that system to get the most of it. Any help would be good.
    I opend a thread in vogons with the problem and all I have done
    Many thanks,
    Jorge
    Last edited by jcarvalho; August 18, 2021, 11:39 PM.

    Leave a comment:


  • cyberluke
    replied
    Solved by removing all duplicate entries of NIC and TCP protocols in Network Neighbours. Then changing address in Device Manager and restarting. Issue with PnP and Windows only Realtek NIC card.

    But the second issue still remains:
    I have also spare 3COM NIC for ISA, but when I run configuration utility I see BOOT ROM is enabled, but it reports address 0H. I cannot change this address. That is very strange and XT-IDE will not show up on this one. Another 3COM ISA can be changed. I guess it is different model or something is faulty on this one.

    Leave a comment:


  • cyberluke
    replied
    Hi, I discovered strange issue. I already have 5 computers running XT-IDE. Now I'm trying to make it work on FIC PA-2005 (Via chipset) motherboard with Pentium 133 MMX. Just installed Windows 98 SE on CF-IDE (32GB).

    Every time I restart (warm restart) the computer, XT-IDE will not show up and BIOS will fail to boot from HDD. On cold reset or computer turn off / turn on, it will work. It seems it is happening in Windows 98 SE.

    The NIC is Realtek PCI with IRQ=10 and I removed all ISA cards. There is only S3 GPU in PCI. This Realtek NIC is supposed to be PnP, but there's no configuration utility. The only way to change stuff is in Windows 98 device manager. So I tried to change address of this Realtek PCI to C800 range as that is where is XT-IDE setup and that's what is reported on the boot.

    But it did not help as well. Am I doing something wrong? I tried disabling as much IRQs as I can, but this does not seem to be IRQ conflict. I tried to change card positions as well. Nothing helps. I spent 2 days debugging this.

    I have 5 Realtek PCI NIC. You cannot change IRQ, but each card have different IRQ by factory. I tried a few of them. It does not solve the problem.

    ---
    I have also spare 3COM NIC for ISA, but when I run configuration utility I see BOOT ROM is enabled, but it reports address 0H. I cannot change this address. That is very strange and XT-IDE will not show up on this one. Another 3COM ISA can be changed. I guess it is different model or something is faulty on this one.
    ---

    Leave a comment:


  • Blazer
    replied
    Originally posted by Krille View Post

    This is weird. I would try disconnecting the CF adapter, the IDE cable and also remove the IDE controller (if possible) to see if these misdetections stop and if so where the problem is.
    Disconnecting the CF adapter and IDE cable made no difference.

    Removing the IDE controller fixed the problem so I replaced the IDE controller with another brand without re-connecting the IDE cable and it has the same problem.

    Master at 170h:
    Slave at 170h:

    If I insert the CF card into the adapter configured as master it works just fine.

    Master at 170h: Sandisk SD-2259-HB
    Slave at 170h: not found

    Which source files are responsible for detecting and displaying the drive information above?

    Thank you.

    Leave a comment:


  • Krille
    replied
    Originally posted by Blazer View Post
    If I boot the system with no CF card inserted then the XUB boot messages for Master and Slave do not say "not found" but are blank.

    Master at 170h:
    Slave at 170h:

    The system then boots automatically from the MFM drive successfully.

    If I run biosdrvs.com it lists 3 drives rather than just the MFM drive.
    This is weird. I would try disconnecting the CF adapter, the IDE cable and also remove the IDE controller (if possible) to see if these misdetections stop and if so where the problem is.

    Leave a comment:

Working...
X