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

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

    Originally posted by Malc View Post
    Like Krille and James said build a new copy of XTIDECFG from the same revision of the SVN Bios
    Just did it. But:
    - the created file is called IDECFG.COM (as defined in MAKEFILE)
    - it is displayed in B/W instead of colour
    - it won't configure my files either
    I checked the MAKEFILE for switches, defines or whatever but nothing found.


    It used to work with the XT_TINY build but i just tried it on a spare raw CF card connected to my XT-IDE REV 1 card and a 16-bit IDE/Floppy card and the Bios R566 saw the CF card but when i ran FDISK it reported " No Fixed Disk Present ", I Re-built the bios adding MODULE_HOTKEYS and went on to FDISK / Partition and format the card with no problems.
    I really feel relieved now someone confirmed my findings.
    With kind regards / met vriendelijke groet, Ruud Baltissen
    www.Baltissen.org

    Comment


      Everything in the Configurator folder is for the old version of the configurator (which is called IDECFG.COM and is used for v1.1.5 and older versions of the BIOS).

      You've probably figured this out already but you should run "make all" in the XTIDE_Universal_BIOS_Configurator_v2 folder to make XTIDECFG.COM.
      Looking for a cache card for the "ICL ErgoPRO C4/66d V"

      Comment


        Originally posted by Krille View Post
        If you feel like testing this, try adding only MODULE_DRIVEXLATE to the DEFINES_XT_TINY line in the makefile.
        Yes that works, I Removed MODULE_HOTKEYS and added just MODULE_DRIVEXLATE and was able to FDISK / Partition and format a raw CF Card with no problems

        Comment


          Originally posted by Malc View Post
          Yes that works, I Removed MODULE_HOTKEYS and added just MODULE_DRIVEXLATE and was able to FDISK / Partition and format a raw CF Card with no problems
          OK, thanks for testing!
          Looking for a cache card for the "ICL ErgoPRO C4/66d V"

          Comment


            Originally posted by Krille View Post
            You've probably figured this out already but ....
            No, and I feel stupid

            you should run "make all" in the XTIDE_Universal_BIOS_Configurator_v2 folder to make XTIDECFG.COM.
            And that worked

            And to confirm Malc's post: adding MODULE_DRIVEXLATE worked fine!
            With kind regards / met vriendelijke groet, Ruud Baltissen
            www.Baltissen.org

            Comment


              XTIDE BIOS and SideCar

              Hi,

              I've recently built a Lo-Tech XT-CF board. It worked perfectly on my Olivetti M24 (idem Logabax 1600 / AT&T 6300), I had been able to setup a 32Gb partition over a 128Mb CF, setup a bootable DOS 3.3 went quite well.

              The trouble comes when I try to use it into my Sidecar [an hardware XT expansion module for the Amiga1000]. the BIOS does not seem to initialize at all while BIOS contents is available under debug at c800. XTCFMODE for devices from 80 to 83 shows "device is not an xt-cf" error.

              Would someone have any suggestion ? Is there a solution to initialize XTIDE after boot time ?

              Regards - Hervé

              Comment


                Hallo Hervé,
                Originally posted by hwarin View Post
                Is there a solution to initialize XTIDE after boot time ?
                Regarding initializing the ROM after boot time should be possible. But the disadvantage: you have to boot from floppy first. As it seems that the BIOS of the Sidecar lacks the feature to initialize external ROMs, my first idea would be to hack the BIOS and add this feature.
                If that is too difficult for the moment, first try it in debug: "g=c800:3". It is just an idea, don't know if it works. If it works, write a little program that those the same and place it in AUTOEXEC.BAT of the floppy. Placing it in CONFIG.SYS should be possible as well but takes a bit more programming effort. I also wouldn't know of any advantage of doing so; I don't know a way to switch to the XT-CF board at that moment. In the AUTOEXEC.BAT is it no problem to switch to an AUTOEXEC.BAT (equivalent) on the CF card.
                With kind regards / met vriendelijke groet, Ruud Baltissen
                www.Baltissen.org

                Comment


                  Did you try enabling late initialisation?

                  Comment


                    No way, Rudd, I've already tried G=C800:3 ... It just hangs .... but it does not kill completely the sidecar as I still can reboot it with CtrlAltDel. (another difference with mt M24 test is the "color" mode, on the M24, I was on MDA, not on CGA ... May be it'll change something ?)

                    James, what are you meaning with "late initialisation" (how to do that) ?

                    I will eventually try with an external video board if I can find one somewhere (true 8 bit VGA) but I'm affraid that it'll make things more complex.

                    Hervé

                    Comment


                      There are several ways the machine's BIOS will initialise option ROMs, and some work in different ways. For the Tandy 1400 laptop Tomi kindly added some very late initialisation code, which needs to be built from source with the option enabled (checkout the code via svn) which was the only way we could get the BIOS to be initialised. It's not perfect, but it works

                      Comment


                        Originally posted by hwarin View Post
                        I've recently built a Lo-Tech XT-CF board. It worked perfectly on my Olivetti M24 (idem Logabax 1600 / AT&T 6300)
                        Does your M24 have a "bus correction kit"? I ask because when I tested the XTCFv2 on my 6300, I got reversed bytes reading the CF card.
                        Offering a bounty for:
                        - A working Sanyo MBC-775 or Logabax 1600
                        - Music Construction Set, IBM Music Feature edition (has red sticker on front stating IBM Music Feature)

                        Comment


                          Originally posted by Trixter View Post
                          Does your M24 have a "bus correction kit"? I ask because when I tested the XTCFv2 on my 6300, I got reversed bytes reading the CF card.
                          It should work if using 8-bit PIO transfer mode (which is the default setting).
                          Looking for a cache card for the "ICL ErgoPRO C4/66d V"

                          Comment


                            James,

                            I've not went to the source code yet (lot of things to setup ...) - I did nit find any reference to a "very late initialisation" but found another reference to "late initialisation" there (with a BridgeBoard !) http://www.vogons.org/viewtopic.php?t=30008 that exposes this solution : "Extract the files from the XTIDE BIOS zip and run idecfg.com. Select "Load BIOS from file" and select ide_at.bin. Select "Configure XTIDE Universal Bios" Select "Late initialisation" and change it to N. Select "Late initialisation" again and change it to Y. Select "Back to previous menu" and then select "Flash EEPROM" Ensure that the "Generate Checksum byte" is set to Y. Select "Back to previous Menu" and then "Exit to DOS" It will now ask you if you want to save the BIOS and say Yes."

                            Also, I found somewhere a thread about a Tandy 1400 discussing about "late initialisation", saying it was default seting for XT class BIOS (my actual option) - I'm using actual r566 IDE_XT.BIN.

                            Regards - Hervé

                            Comment


                              Trixer,

                              I can confirm, it works strait on the M24 (with default PIO mode).

                              Comment


                                Good to know, thanks guys. Now I have another use for it
                                Offering a bounty for:
                                - A working Sanyo MBC-775 or Logabax 1600
                                - Music Construction Set, IBM Music Feature edition (has red sticker on front stating IBM Music Feature)

                                Comment

                                Working...
                                X