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

HIMEMV2 or equivillent PROM

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

  • eric8x
    replied
    agreed

    Leave a comment:


  • Chuck(G)
    replied
    Thanks for the correction. I'dve thought that DOS=UMB would result in most of DOS loading in UMB, but I guess not--it requires HMA and that isn't going to happen. Perhaps I should RTFM more...

    Leave a comment:


  • ibmapc
    replied
    Originally posted by Chuck(G) View Post
    Yup, with the UMB driver, you can load DOS high, along with drivers and TSRs. Pretty cool on a resource-limited system. EMM386 or HIMEM not required.
    Minor Correction
    Loading DOS high is not possible with this arrangement since there is no "HIGH" memory, only UMB. If I understand correctly, "HIGH memory" is the segment immediatly beyond 1 megabyte.

    However, even with my setup, which incudes EGA and Hard Disk which both use portions of "Upper Memory", I am able to use one block of 128K of UMB. I can load dosdata, command.com, several device drivers, and TSR's in that 128K of UMB. My config.sys starts out as follows

    device=c:\use!umbs\clearmem.sys d000 2000 (clearmem.sys Chuck(G)'s wonderful creation)
    device=c:\use!umbs\use!umbs.sys
    dos=umb
    dosdata=umb
    shell=c:\dos\command.com /h/e:512 c:\dos /p
    devicehigh=c:\hotshot\fdd.sys
    devicehigh=c:\dos\setver.exe
    devicehigh=c:\dos\ega.sys

    If I change the "dos=umb" to "dos=high,umb" most of the system kernal still loads in low memory, since there is no actual "HIGH" memory. However the "dosdata=umb" puts 17,800 bytes of the system kernal into UMB. And the "shell=command.com /h ..." puts all of command.com in UMB. Kind of inconsistent here, because one could interpret the /h as referring to "HIGH memory, but it actually refers to UMB, or "UPPER momory.

    Check out the folowing This is the current memory configuration for my 5155. Note that I have 608,960 bytes of base memory free and there is still 91,184 bytes of "UPPER" memory available for more drivers and tsr's.

    Leave a comment:


  • MikeS
    replied
    Originally posted by Chuck(G) View Post
    Without the board on hand to trace out the circuitry or at least a schematic, it'd be pretty close to impossible for someone like me. But given one or the other, it'd be pretty straightforward, I'd think.
    Pshaw! Nothing's impossible for you!

    Not much point though unless somebody's seriously interested as the OP was.

    Leave a comment:


  • Chuck(G)
    replied
    Without the board on hand to trace out the circuitry or at least a schematic, it'd be pretty close to impossible for someone like me. But given one or the other, it'd be pretty straightforward, I'd think.

    Leave a comment:


  • MikeS
    replied
    Originally posted by Chuck(G) View Post
    Yup, with the UMB driver, you can load DOS high, along with drivers and TSRs. Pretty cool on a resource-limited system. EMM386 or HIMEM not required.
    Pretty cool indeed; I don't really need one myself, but I wonder if with possibly a little rearrangement of the I/O pins one of these GALs would be a direct drop-in replacement for those boards with a 20-pin PAL?

    Leave a comment:


  • Chuck(G)
    replied
    Originally posted by MikeS
    So, do I gather from all this that if we put in one of these custom GALs we get usable UMBs on our XT clones, not just RAMdisk & print buffer memory?
    Yup, with the UMB driver, you can load DOS high, along with drivers and TSRs. Pretty cool on a resource-limited system. EMM386 or HIMEM not required.

    Leave a comment:


  • MikeS
    replied
    Out of 6 loose MBs two of mine are the same as Modem7's, i.e. 18x256 + 18x64 with a 20-pin PAL (U103) at the end of the ROM row and a 256/640 jumper, although one PAL is a 14L4CN while the other is a 16L8ANC (which is maybe also what Modem7 meant).

    I'm pretty sure I've got a few more in cases, including IIRC at least one 1024K version; I'll have a look if I get a chance.

    So, do I gather from all this that if we put in one of these custom GALs we get usable UMBs on our XT clones, not just RAMdisk & print buffer memory?

    Re Chuck's latest post which crossed mine in cyberspace, the rest of my boards are the same as his, i.e. 18x256, 4x4x64 and 2x64, both 10MHz and 12MHz. Also, these boards only have one 28-pin spare ROM socket instead of six like the above-mentioned boards, presumably for a larger all-in-one BASIC ROM.
    Last edited by MikeS; December 12, 2011, 12:16 AM. Reason: Comment on Chuck's post

    Leave a comment:


  • Chuck(G)
    replied
    Useful info, thanks. Another clone i looked at--a 10MHz turbo board--uses 2 banks of 41256 and fills out the remainder with 4464 and 4164 (for parity). Obviously some vendors followed the IBM model and others didn't.

    Leave a comment:


  • modem7
    replied
    Originally posted by Chuck(G) View Post
    Here's my question to the XT clone community at large.
    If you have a XT clone motherboard with 4 x 9 chip RAM organization that accepts 256Kb DRAMs in at least the first two ranks, do you also have a socketed 16-pin bipolar ROM on your board?
    I have just now examined five of my six clone XT motherboards (one is in storage). Only one of those five has the 4x9 RAM chip arrangement. 256Kbit chips in banks 0/1 and 64Kbit chips in banks 2/3. The motherboard is labeled "X'GOLDEN TURBO-BOARD".

    Close to the RAM banks is a socketed PAL16L8ACN. Near to the PAL16L8ACN is a "256K/640K" jumper, of which one pin is connected to pin 18 of the PAL16L8ACN. That pin is grounded for 640K and is pulled high for 256K.

    So, 20-pin, not 16-pin, and PAL, not PROM.

    Leave a comment:


  • Chuck(G)
    replied
    I hauled out one of my XT clones and looked at the motherboard. It appears to be a Turbo 640, or a close relative, with an ERSO BIOS.

    One thing that caught my eye was a socketed 16-pin IC just to the right (looking from the rear) of the BIOS sockets, near the edge of the PCB. It turned out to be a 82S129 PROM, which is the Signetics equivalent of the 24S10 PROM on the 5160. I suspect, but haven't verified, that the HIMEMV2 mod will work as-is on this board.

    Here's my question to the XT clone community at large.

    If you have a XT clone motherboard with 4 x 9 chip RAM organization that accepts 256Kb DRAMs in at least the first two ranks, do you also have a socketed 16-pin bipolar ROM on your board?

    Since the ERSO design was the reference design for most Taiwanese XT clones, I suspect the answer will be "yes". There are later designs where the last two ranks of RAM are replaced with 4464-type chips, but they're easily recognizable, as they don't have the "block" of 36 chips arrangement.

    Leave a comment:


  • Chuck(G)
    replied
    Reading books about machine architectures can induce coma in many people. And I'm the wrong one to recommend a tutorial--the best thing to do is to ask someone who's just learning about the subject.

    That being said, take a look at this tutorial that you can run on your 5155. I think it's pretty cool.

    Leave a comment:


  • ibmapc
    replied
    That did it!!
    Now boots everythime without the Parity Check. Thanks again Chuck.
    And by the way, you are right, of coarse,I do need to learn assemly. I guess I've felt that it was beyond my mental abillities. Maybe you could recomend a good book? Something like Assembly X86 for old Dummies?

    Best regards,

    Greg

    PS Boy o Boy, this 5155 is a real Hot Rod now!

    Leave a comment:


  • Chuck(G)
    replied
    I found some time to throw together CLEARMEM.SYS (attached).

    Invocation is easy, just put it in your CONFIG.SYS file ahead of the USE!UMBS.SYS command. It takes two arguments, both in hex. The first is the starting segment address of an area to be zeroed; the second is the hex number of paragraphs to clear. CLEARMEM releases its memory after it clears, so it doesn't occupy any space permanently.

    So, to clear the range between D000:0 and E000:FFFF, use the following statement in CONFIG.SYS:

    DEVICE=CLEARMEM.SYS D000 2000

    In other words, clear 8192 (decimal) paragraphs, or 128K starting at segment D000.
    Attached Files

    Leave a comment:


  • Chuck(G)
    replied
    Originally posted by per View Post
    you can run program files from config.sys, at least in later versions of DOS (unless I'm slightly mistaken).
    Yes, but they're run after device drivers have been processed, in the same way that SET statements are processed in the CONFIG.SYS file.

    If I get a few minutes this afternoon, I'll make the driver mods, rather than waste time gumming the subject to death.

    Leave a comment:

Working...
X