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

AST Six Pack issue

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

    AST Six Pack issue

    Greetings again, after resolving my clock issue, i now have another one. Drivers for the EMM on the AST Six Pack premium. I have googled them and not found much, does anyone in the forums have such files? Also, is there a way to get the 4 floppy controller to exist with ANY vga card? Both of mine seem to want to occupy the hole that ANY of my vga cards want, including my Headland.
    Last edited by k2x4b524[; February 26, 2012, 07:35 PM. Reason: It's not a plus, it's a premium.
    Nothing beats the roar of a 36yr old drive coming to life after a decade in storagg

    #2
    I hate to do this, but bump..
    Nothing beats the roar of a 36yr old drive coming to life after a decade in storagg

    Comment


      #3
      I do have the SixPackPlus disk that does have the EMM driver, however is your six pack plus above and beyond the 640k?
      Speaking of your clock issue, what issue did you have? The issue I am having is that the ASTCLOCK software spits back out a backwards date like 99/17/23 and 99:99:99 for a time.
      Daniel P. Cayea - The Lyon Mountain Company - Plattsburgh, New York 12901
      Vintage Equipment: IBM 5150 * IBM 5161 * ThinkPad 770ED
      Modern Equipment: MacBook Pro 13 * Alienware M15R3

      Comment


        #4
        my six pack premium has 256kb that is above the 640k line, the rest is serving as conventional on a 64kb-256kb system board, hence the need for the EMS drivers, i would like to use those, and q-ram on this board. As for the clock drivers, don't use the clock on the six packs, my premium's clock refuses to go above Y2K, get a Dallas 1216E Smartwatch and plunk that guy under your F000 Bios, you'll get better results, and the utilities aren't TSRs. Could you email me a copy of your SixPack Plus drivers?
        Nothing beats the roar of a 36yr old drive coming to life after a decade in storagg

        Comment


          #5
          Give me a day or so to convert it to modern format for transport As for the Dallas 1216E, is it a chip that actually sockets between the motherboard and the BIOS ROM?
          Daniel P. Cayea - The Lyon Mountain Company - Plattsburgh, New York 12901
          Vintage Equipment: IBM 5150 * IBM 5161 * ThinkPad 770ED
          Modern Equipment: MacBook Pro 13 * Alienware M15R3

          Comment


            #6
            Maybe this it what you looking for?

            http://ibm-pc.org/drivers/memory/memory.htm

            AST Superpak Utilities (1985)
            AST SixPakPlus Utility Disk - DOS
            THE BIOS MASTER

            Comment


              #7
              Thank you both of you
              And yes, the 1216E sits between the bios and the motherboard.
              Nothing beats the roar of a 36yr old drive coming to life after a decade in storagg

              Comment


                #8
                @k2x...
                What is the best place to acquire said Dallas chip. Are there any modern sources?
                Daniel P. Cayea - The Lyon Mountain Company - Plattsburgh, New York 12901
                Vintage Equipment: IBM 5150 * IBM 5161 * ThinkPad 770ED
                Modern Equipment: MacBook Pro 13 * Alienware M15R3

                Comment


                  #9
                  http://www.maxim-ic.com/datasheet/index.mvp/id/2638
                  Nothing beats the roar of a 36yr old drive coming to life after a decade in storagg

                  Comment


                    #10
                    Once you get it, how do you program it?
                    Daniel P. Cayea - The Lyon Mountain Company - Plattsburgh, New York 12901
                    Vintage Equipment: IBM 5150 * IBM 5161 * ThinkPad 770ED
                    Modern Equipment: MacBook Pro 13 * Alienware M15R3

                    Comment


                      #11
                      I have one smartwatch installed under the BIOS EPROM on a Flytek motherboard (STJUKO TURBO Motherboard)

                      Please also look on my thread:
                      http://www.vintage-computer.com/vcfo...rial-com3-port

                      More detailed info:
                      http://www.brutman.com/PCjr/DS1216E.html

                      1.you need to pick the ROM chip that responds to memory accesses at F000:000 (mostly the bios rom, not always!)

                      2. Download the software: http://www.brutman.com/PCjr/downloads/ds1216e.zip

                      3. Run program TEST-CLOCK.EXE to verify if the clock is working and programmable..

                      4. Run CLOCK.EXE EVERY TIME you boots / reboots the system.. Better is to set a line in autoexec.bat..

                      5. With CLOCK.EXE you also can set the date and time and day...

                      The clock is only working when loading CLOCK.EXE on boot..
                      How to set it, just read the included manual / documents..


                      The good of this dallas solution..

                      Its working fine, and Y2K is supported up to 2099 or so..
                      No ISA card with clock needed (mostly they are dead, or doesnt support Y2K..)

                      Only a little bad is.. Older system diagnostics doesnt detecting this dallas..
                      The other good is, its just ****ing working under compaq DOS 3.31 !!

                      I think you wont find a better solution than this..
                      Last edited by Robin4; March 1, 2012, 05:22 PM.
                      THE BIOS MASTER

                      Comment


                        #12
                        EDITED POST

                        I was messing around with the ASTClock.com program today and although it reports the Year incorrectly, MsDos 6.22 ends up getting it right.

                        You can see where the astclock.com program sets the year to 99 at the MOV,AL 63 instruction near location memory offset 0237 (debug).

                        The version on the astclock program I debugged was 1.10
                        The MSDos version I have loaded is 6.22

                        If someone really wanted to patch the astclock.com program to display the date correctly this might be a good place to start looking.

                        Enjoy.


                        Matt
                        Last edited by FireBox; March 4, 2012, 11:15 AM.

                        Comment


                          #13
                          Originally posted by FireBox View Post
                          I was messing around with the ASTClock.com program today and although it reports the Year incorrectly, MsDos 6.22 ends up getting it right.
                          When I read that, I recalled that the issue had been mentioned before:
                          http://www.vintage-computer.com/vcfo...read.php?23343

                          Comment


                            #14
                            So I have my DS1216E, lovely little gem, but I find that the socket it comes in is a 28 pin socket and not the 24 pin socket that the ROM chip sits in. I'm assuming that the BIOS is the ROM that sits in U33 on a 5150.
                            Daniel P. Cayea - The Lyon Mountain Company - Plattsburgh, New York 12901
                            Vintage Equipment: IBM 5150 * IBM 5161 * ThinkPad 770ED
                            Modern Equipment: MacBook Pro 13 * Alienware M15R3

                            Comment


                              #15
                              Yeah you need an adaptor to use 'normal' ROM's (27xxx) in a 5150/60 - so not suprised it doesn't fit :/
                              Hopefully someone has a grand idea to assist, I didn't even think of that issue until you mentioned the pin difference.
                              Twitter / YouTube

                              Comment

                              Working...
                              X