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

  • jakeh12
    replied
    Originally posted by FireBox View Post
    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
    Hey, just an update. I successfully patched ASTCLOCK.COM yesterday to show Y2K years properly. I thought it would be nice to share in this thread.

    Solution:
    http://www.vcfed.org/forum/showthread.php?62497

    Leave a comment:


  • ibmapc
    replied
    Originally posted by lyonadmiral View Post
    @ibmapc
    Thanks for the offer, but I traded the 24 to 28 pin adapter.
    Hey, Lyonadmiral, check THIS out. It's the manual for the No Slot Clock. If you look at page 48, it describes how to modify the No Slot Clock to work in a 24 pin socket without an adapter! Just solder a jumper between pins 1, 26, 27, 28 and plug it into the 24 pin socket with pins 1,2,27,28 hanging over the end, then, plug the rom in. Page 49 tells you which socket to put it in.

    Leave a comment:


  • ibmapc
    replied
    Originally posted by lyonadmiral View Post
    @ibmapc
    Thanks for the offer, but I traded the 24 to 28 pin adapter.
    Let me know if you change your mind and want to try to put DS1216E in your 5150. Just tryin' to pay forward some favors others here have done for me. People on this forum are great! I really think that it's worth the trouble. I've had two of them in my 5155. The first one lasted 24 years before the battery died. The second one was purchased from Maxim about a year ago. Previously, you mentioned putting it in your XT. Let us know how it works out.

    Leave a comment:


  • lyonadmiral
    replied
    @ibmapc
    Thanks for the offer, but I traded the 24 to 28 pin adapter.

    Leave a comment:


  • ibmapc
    replied
    Originally posted by lyonadmiral View Post
    What I think I'll end up doing is just putting into my XT, and if anyone here wants an adapter I will sell it to you guys. Much more simpler.
    Lyonadmiral, I have some 27c256's and a programmer. If you send me a PM with your Bios version and address, I could program one with the appropriate bios and send it to you for the cost of shipping. Let me know if your interested.

    Leave a comment:


  • lyonadmiral
    replied
    What I think I'll end up doing is just putting into my XT, and if anyone here wants an adapter I will sell it to you guys. Much more simpler.

    Leave a comment:


  • modem7
    replied
    Originally posted by lyonadmiral View Post
    Crap, well anyone else out there watching, can you confirm is it a futile mission? 24 pin to 28 pin adapter to plug in my Dallas No-Slot-Clock, and then plug my 24 pin ROM into the 28 pin socket on the clock?
    The 24 pin U33 BIOS ROM will not work in the 28 pin socket - different pinouts.

    What should work is what SpidersWeb wrote: The adapter you bought into the U33 socket, then the DS1216E into the adapter, then a 27xxx (or 27Cxxx) EPROM copy of the U33 ROM into the DS1216E.
    1. No guarantees.
    2. The U33 socket sits at address FE000, not F0000, and so the software at mbbrutman's web site is not expected to work. Try alternate DS1216E software.
    3. When creating the 27xxx EPROM copy of the U33 ROM, the 8K image of U33 needs to go into the last 8K block in the EPROM (because of the particular adapter your bought).

    Basically you will be doing what is described in the OPTION 1 area of http://www.minuszerodegrees.net/5150_u33.htm , except that you will be putting a DS1216E between the adapter and the 27xxx EPROM.

    Leave a comment:


  • lyonadmiral
    replied
    Crap, well anyone else out there watching, can you confirm is it a futile mission? 24 pin to 28 pin adapter to plug in my Dallas No-Slot-Clock, and then plug my 24 pin ROM into the 28 pin socket on the clock?

    Leave a comment:


  • SpidersWeb
    replied
    I haven't checked the pinout, but I'd expect you can't install the original ROM in the adaptor. I'd expect you'd need to mount the adaptor on TOP of the existing ROM (if thats even possible), and install the DALLAS in the adaptor. Or, make a 27Cxxx ROM to replace the original, and install that and the DALLAS in the adaptor.

    Someone else would/will need to confirm that.

    I had it a bit easier, my XT has a unit which goes under the CPU.

    Leave a comment:


  • lyonadmiral
    replied
    I'll get it mounted in U33, of course my problem is where U33 is on the motherboard, it is a tight fit up against the floppy disk drive. Now since the U33 ROM chip is smaller than the Dallas, will I need another adapter for that or can I mount it as is, 24 pin ROM in a 28 pin socket?

    Leave a comment:


  • SpidersWeb
    replied
    Yep, that's the correct adaptor.

    Just a case of getting it mounted/secured on top of the U33 or copying the ROM to a 27 series - unless the DS1216E can operate off the spare ROM holder?

    Leave a comment:


  • lyonadmiral
    replied
    I just ordered one of these from Retro Innovations.

    http://store.go4retro.com/2364-adapter/

    I hope someone can confirm that is indeed what I need so I didn't just waste 9 bucks.

    Thanks,
    Dan

    Leave a comment:


  • SpidersWeb
    replied
    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.

    Leave a comment:


  • lyonadmiral
    replied
    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.

    Leave a comment:


  • modem7
    replied
    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

    Leave a comment:

Working...
X