Jump to content

wierd_w

Members
  • Content Count

    1,654
  • Joined

  • Last visited

Everything posted by wierd_w

  1. Dont have an exact one, but I would think it would work with generic drivers for that chipset. Lots of generic 1mb VGA cards were made for early PCI systems with that chipset, which is what I presume this PC-104 board is meant to work as. Positive ID shouldn't be necessary, no?
  2. XT IDE bios is able to do this, but Zap!'s eeprom is too small to hold the reconfigured bios.
  3. See also, this video from Adrian's Basement.
  4. The step motor is basically just that. It is functionally not much different from the kind used in modern 3D printers. The armature shaft is exposed at the bottom, and the bearings contact the armature shaft. As such, it is possible to wash out the bearings (VERY CAREFULLY) with alternating treatments of electrical contact cleaner (to get old oxidized oils out), and then lubricate the bearings with a light machine oil. (I am partial to A1 oil.) If the bearings are seized, use a drop of knock-er-loose penetrating oil first. the ST-225 has a factory test jumper that makes the head assembly do endless full actuations over and over. This is useful to make the drive exercise itself without a computer attached. the contact cleaner treatment is usually not needed though, unless there is clear and obvious signs of lacquered oil on/around the armature shaft of the stepper motor. For ST-225, the step motor is the small motor in the corner. Avoid the motor shaft underneath the plastic skid protector-- that is the platter motor. If you oil that, make sure it is some tiny fraction of a drop, since it will wick up the shaft, and can then splatter out onto the platters if you apply more than that, and that would be most unfortunate indeed. While I do not encourage anyone to open up the disk drive, this is what it looks like inside. As you can see, the step motor that drives the head is actuating a control arm, and is quite distant from either the platters or the head assembly arm. As such, it is pretty safe to oil the shaft. The shaft of that step motor is exposed on the bottom, as seen here:
  5. OK, I am going to kick this out here: Zap! would like to have the MFM controller and his shiny hawt XT-IDE to co-exist. Here is the issue: These things TOTALLY CAN coexist. However, the MFM controller will always enumerate its drives in the interupt handler table FIRST. This means that drive 80h is going to be living on the MFM controller. (No bueno, if you want to boot the CF card, for reasons that should be plenty aparent.) XT-IDE can be turned on with a boot menu, but the rom in his controller did not have this built in the tree when it was created. (because cheap seller, I think.) The XT-IDE can be instructed to boot from a device OTHER than 80h, but when attempting to flash, it complains that the eeprom type is not large enough after setting the option. I have advised him that at this time, his options are: Boot from the ST-225, and have DOS 6.22 on there, so that he can access the CF card as drive D. or Forego coexistence for now, until we can devise a better solution. (Such as getting a larger eeprom into his socket, and flashing it with a more capable XT-IDE build) I am open to suggestions however.
  6. Oh yeah-- I had forgotten about the MBR limitation. D'oh
  7. Microsoft released an LBA48 patch for XP, but needs service pack 1. http://smallvoid.com/article/winnt-lba-48-bit.html Your boot volume must be on a system that has bios-level 48 bit LBA support though. (So, either a very recent BIOS implementation, or a DDO.) OTHERWISE--- You need a smaller (under 137gb, iirc?) boot volume, and then once the OS loads, MS's 32bit disk drivers handle all the heavy lifting. (partition your device accordingly.)
  8. Ultimately, they do the same thing. The XT-IDE bios really does the same thing, all things considered. It can even be loaded into an UMB slot, and then executed with debug, if you REALLY want. (There were some enterprising discussions about doing that online one time I looked into it.) DDOs win out when not baked into an actual controller though, in that they work with arguably a broader range of controllers and drives.
  9. Cyrix got a bad name for itself back in the day, by not being "completely compatible", and causing all manner of headaches. A specifically high profile instance, were Cyrix's 6x86 "Pentium compatible" processors. The FPU implementation in those would break HORRIBLY when trying to play Quake. They were almost without exception synonymous with "Trash."
  10. For a drive that size, you will *NEED* the DDO. Even with the DDO installed, DOS6.22 has a size limit of 2gb. THAT limit is imposed by DOS. You could maybe kinda-sorta get around it by abusing windows 98SE as if it were DOS (Using the EBD, and copying the C:\windows\command directory from a functional windows install to C:\DOS, and pretending it is "Dos 7" ahem) so that you can have FAT32 support, OR by going straight to FreeDos, and going that route. To set that up, you would need a bootable DOS diskette, *AND* you would need to have created the disk manager boot diskette. Boot on the disk manager diskette, and do the guided installation. It will set your BIOS to the correct custom geometry type for you (DONT TOUCH IT afterwards!), then install the DDO in sector 0 of the drive. The DDO will then intercept all BIOS disk calls, and will do software translation to handle large disks over 8gb in size.
  11. I would not steer anyone toward anything made by cyrix. The intel one I linked you to is the genuine article.
  12. windows 95 will run very poorly on that system. It is the lowest tier 386 Intel made. (SX-25) It is also an old 30 pin SIMM based system, and will have dog-slow memory access speeds. All around, its a budget system from back in the day. It wouldnt have won any speed competitions then, and certainly wont now. I would suggest staying with DOS or DOS + Win3.11 I would suggest DOS6.22 I would suggest between 8 and 16mb of FastPage 30 pin simms. (8 1mb modules, or 8 2mb modules, all identical!!) I would suggest a nice jumpered soundblaster 16. (Avoid plug and play ISA cards like the plague!! They will almost certainly not work properly in this system! It predates PnP!!)
  13. Well, just looking at it--- It has a 386 SX processor, and a LIF socket for QFD package 387 coprocessor. It uses a 3.6v lithium battery. (size 2AA) It has a maximum onboard RAM capacity of 32mb, assuming you stuff those 30 pin simm slots with the more expensive 4mb modules. I would suggest 1mb or 2mb modules though. (It probably only supports up to 16mb, with 2mb modules. This looks like a budget system intended for an office workstation type application. 4mb modules would be a crapshoot.) It has a chips and tech F82C836 (SCATx) chipset. (more information about the RAM capabilities can probably be found by looking up the chipset rather than the board) It has an integrated western digital disk controller, which handles both IDE hard drives and the floppy drive. (It probably has the 8gb limitation, and will likely need a DDO to use anything bigger. See Phil's computer lab for details) It uses a proprietary power connector. I certainly HOPE that your system came with the riser. You will need it to plug anything into its ISA bus. Assuming you do have it, you can plug any old ISA card into it. (sound blaster, AST ram expansions, etc.) Based on your description, you have 2 512kb 30pin simms installed, giving you a whopping 1MB total memory. (Basically, 640k + 384K used predominantly for shadow ram purposes. From the image of the BIOS, it is snarfing down 128kb of RAM for shadowram purposes, leaving 256k of extended memory left over.) That chipset is supported by a hardware UMB and EMS driver, if you dont want to use EMM386.exe to get access to upper memory blocks. https://www.pcorner.com/list/UTILITY/UMBDVR22.ZIP/INFO/ For BIOS upgrades... I have no idea where you would get one, but back in the day, there was a 3rd party bios company called MrBios. They had 3rd party BIOS images (and chips) for a number of systems. I will see if yours was listed. (looked, No dice. I would not recommend anyway.)
  14. I have identified the remaining cards in this system. The multi-IO is an AST mini IO II, which contains a realtime clock chip. (SCORE)-- It DOES have a 15 pin gameport header. I have advised Zap! to get an appropriate IDC pigtail. I also forwarded him to an archive with appropriate AST clock utilities. https://stason.org/TULARC/pc/io-cards/A-B/AST-RESEARCH-INC-Multi-I-O-card-I-O-MINI-II-202123.html The floppy disk controller is a low density IBM diskette controller. http://www.minuszerodegrees.net/oa/OA - IBM 5.25 Diskette Drive Adapter.pdf The final, short card in there is an IBM async card; a glorified serial port. http://www.minuszerodegrees.net/oa/OA - IBM Asynchronous Communications Adapter.pdf
  15. Is this your motherboard? (I see elsewhere that the model you specc'd is also listed as Z-320SX-40, which is what is pictured here.) Like most ZENITH systems I remember seeing from that era, it uses a backplane riser that is 90 degrees. Basically any old card can go in the riser.
  16. It is, but spinrite wants a high density diskette drive, and this is low density.
  17. Zap! tells me there are still some issues with the drive. Given it is over 30 years old, that is not surprising. He needs to aggressively test the platter surface; it's possible the coating has warn off over 30 years intermittent use. I suggested a dos 6.22 boot disk with scandisk on it. (I don't think norton disk doctor would run on dos 3.1)
  18. Not much you can do with the XT aside from enabling ansi graphics with ansi.sys. It cannot access memory above 1mb, so you cannot use the HMA, or things of that nature.
  19. I have been helping Zap! get this beast going. (long chain of PMs) One of the items in there is a rather unusual bit of kit-- A DCA 05-0060-03 PC/3278 IRMA adapter, which was used to interface the computer with an old IBM mainframe. In his picture dump, it is the third card from the right, as seen from the back. I have no idea what he is going to do with it, since it is really just an interesting bit of esoterica without a mainframe to attach to... but who knows. Mentioning it here might get the attention of somebody that needs one (and does not want to hork out 80$, like that Ebay seller wants.) It is my understanding that one can get it to work with a more modern IBM server, like an AS/400, but again-- you would need one of those beasts. Bitsavers has some limited documentation about the device: http://www.bitsavers.org/pdf/dca/irma/ and archive.org has a selection of software that could be used with it, preserved via wayback: https://web.archive.org/web/19970419174451/http://supportweb.attachmate.com/file/filelibrary.htm (DCA was purchased by Attachmate. The old cards are supported) The hard disk controller is an IBM/XEBEC version 3. I helped Zap! get through the low-level initialization and high-level partition/format for that drive. (Seagate ST-225, back when seagate made bulletproof drives.) It was having issues locating sectors, and I suspect it had gunky bearings on the drive sled stepper motor. It's since been cleaned up, and the sector markings re-created. (I suspect that it had been LLF'd while the head actuator was gunky. After cleaning, it still could not locate sectors. Either the sector marks themselves just bitrotted due to random inversion events, or they were not in the correct positions. A new LLF after reconditioning the stepper seems to have sorted it, but sadly nuked any data on there.) Seems to be running fine now.
  20. Sounds like your IP Cop thinks that they are "RIGHT!", and wont budge. Consider reaching out to the AtariAge ops, and having them contact Spring. You have to make this as nasty for the IP Cop as possible, so that he/she sees the light.
  21. The whole program is not visible. Part of the display suggests it is part of a function plotter program. Subsequent images suggest the plotter program is stopped from the disk getting full, while attempting to BSAVE the data stored in an array. (This is usually used to store raw image data from MS Qbasic.) This halts the program, and drops it the basic interpreter prompt. Some of the program's listing is displayed. Key portions of the program are not in the listing. However, the program appears to be an Fx(X,Y) function plotting program, with routines to save the plotted function's image to disk, and functions to print the resulting function graph to a printer of some kind.
  22. When one frog alien loves another frog alien a whole lot, and holds hands....
  23. Its probably just some overzealous content cop in their org, coupled with a lack of communication inside their org. EG, person tasked with stopping people from selling merch they dont have license to sell--- bumps heads with "No, totally has a license, but we just failed to annotate that on their account in a meaningful fashion."
  24. The biggest risk factor when using a commodore/ti video cable is where the +12v lead is on the DIN. Since we have a nicely labeled +12v lead going to the video sub board, a multimeter test can be used. (+12v is used to power an external RF modulator, if needed. For plainly obvious reasons, that should not be put through a composite video circuit.) Additionally, composite video is well labeled also. Continuity testing should give those also, along with audio. So, getting video pinout should be a short process with a multimeter. Power is the straggler.
×
×
  • Create New...