Jump to content

Larry

+AtariAge Subscriber
  • Posts

    5,492
  • Joined

  • Last visited

Posts posted by Larry

  1. Got another one going... haven't done any kind of real testing yet but the COPY /R D1: D3: appears to be going fine. It's pretty quiet too.

     

    • Seagate ST15150N - 4.3gb

    RWTEST 512b sectors

    Writ: 30441.2179

    Read: 40483.6815

    Avg: 35462.4497

     

    (snip...)

     

    The ST15150N is a 1/2-height (1.6"), early-model 7200 rpm drive?

     

    Can you determine the drive firmware version of yours?

     

    I see that these drives seem to be fairly abundant and reasonably inexpensive.

     

    -Larry

  2. I took one more (unsuccessful) try at the ST31230N.

     

    Once and only once, I got it to register a block size of 512 and was able to successfully save the configuration data. But after that, no luck. Tried every logical combination of jumper settings that I could think of. I'll have to wait for some different drives to test.

     

    -Larry

  3. As of this evening, after tearing my hair out for several weeks :cool: , I have 2 SCSI drives working Rock Solid with the 1.4b3 firmware using a stock 130XE, ICD 1Meg MIO (unmodified except for FW). My tests were done with 2 DOS versions (SpartaDOS 3.2g and SDX 4.42) using a mixture of densities (256b and 512b per sector) and these drives:

    • Seagate ST32430N - 2.1gb
    • Seagate ST31055N - 1gb

    Both of these drives can supply term power to the SCSI bus which is necessary on the unmodified MIO as Warerat has pointed out.

    (snip...)

    And both drives are pretty fast. KMK's RWTEST on the ST31055N reports:

     

    512bytes/sector

    Write: 38125.4088

    Read: 41335.9696

    Avg: 39730.6892

     

    256 bytes/sector

    Write: 21226.5789

    Read: 23099.5124

    Avg: 22163.0456

     

    What kind of RWTEST numbers did you get from the ST32430N?

     

    -Larry

  4. See the arrows with the '1' in a circle pointing to the jumpers I have on... 1,2,4,8 are all on... the rest are off.

     

    On my ST32430N I have 1,2,8 on which may be what you have because the 2 part numbers are pretty close.

     

    Ah... Got it -- thanks.

     

    -Larry

  5. ...

     

    Unfortunately, my very nice (silent and cool) ST32130N does not work, but I'd like to check all my jumper positions versus yours.

     

    Could you please post the list of your jumper positions with the Seagate descriptions (TE, ME, MD, etc.)

     

    Sure... remember this is for UNMODIFIED MIO (no term power from MIO).

     

    ST31055N

     

    post-8623-1240493085_thumb.jpg

     

    Something to remember - some Seagate drives have Parity 'enable' jumpers and some have Parity 'disable' ones. My ST32430N has PE.

     

    Thanks.

     

    Not to be redundant, but you have all the jumpers as shown, or are some of them not attached (e.g. ME, DS)?

     

    Yes, my drive is marked for Parity Enable "PE" And, sorry, I keep transposing my drive numbers -- it is a ST31230N.

     

    -Larry

  6. As of this evening, after tearing my hair out for several weeks :cool: , I have 2 SCSI drives working Rock Solid with the 1.4b3 firmware using a stock 130XE, ICD 1Meg MIO (unmodified except for FW). My tests were done with 2 DOS versions (SpartaDOS 3.2g and SDX 4.42) using a mixture of densities (256b and 512b per sector) and these drives:

    • Seagate ST32430N - 2.1gb
    • Seagate ST31055N - 1gb

    Both of these drives can supply term power to the SCSI bus which is necessary on the unmodified MIO as Warerat has pointed out.

     

    (snip...)

     

     

    Congrats on getting these two drives working!

     

    Unfortunately, my very nice (silent and cool) ST32130N does not work, but I'd like to check all my jumper positions versus yours.

     

    Could you please post the list of your jumper positions with the Seagate descriptions (TE, ME, MD, etc.)

     

    I am glad to see you got a couple of Narrow drives working, since that avoids adding adapters.

     

    Thanks,

    Larry

  7. I'm getting ready to try out an ST31230N drive with the MIO. It is the only drive on the bus.

     

    Among other options the drive jumpers allow the following:

    ...

    Termination enable/disable

    Term. power supplied from drive/not

    Term. power to SCSI bus/not

    Term. power from SCSI bus/not

     

    I need Termination enabled (end of SCSI chain).

    Can I use "Term. power from drive?"

    But I would disable Term. Power to SCSI bus?

     

    So, the termination power would come from the drive, but not be applied to the SCSI bus (back to the MIO)?

     

    I saw the post showing the MIO-supplied term. power, and I can do that, but if I can provide it from the drive it would be easier.

     

    Thanks,

    Larry

  8. That's normal. If you lay down a DD 512 filesystem it will be 32MB. The blocksize you see is what is reported by the drive. The version I'm using (unreleased) has the arithmetic stuff changed and you can toggle between 256/512 and it shows 16383K/32767K, but that only affects the sector size reported back on the Percom config. If you set it for 256 bytes on a 512 byte device it will still do 512 bytes at the physical level but only present the application with 256.

     

    I just looked up your drive and noticed it is a 10,000 rpm drive. Do you think that it would be markedly faster than a 7200 Cheetah (same SCSI generation)? Would you say that it runs cool and quiet?

     

    Can a more modern SCSI drive such as you are using be run with (fairly short) ribbon cable? Or should we stick with a "bundled" cable such as you use?

     

    Thanks,

    Larry

  9. fortunatly, rgb to ybpbr conversion is not that complicated

    but sorry to hear that, as You're using same chips inside Your tv sets as european folks, and not having those connection outside is really worrying

     

    here even worst Crap from china has scart with rgb connected, and ypbpr signals are on a bit higher class equipemnt - a bit only, because most new lcd/pdp panels i've seen has one, even if this is 20" low res (like 640x480 or 800x600) 4:3 low end lcd it might have ypbpr inputs integrated in scart

     

    don't worry though

    there is RGB to VGA adapter in plans, and all needed signals will be provided to convert RGB into something else (composite, s-video, or ypbpr)

     

    Thanks, Candle!

    -Larry

  10. sorry for double post :/

     

    anyway commodore 1084 or philips 83something-ii are perfectly capable of displaying vbxe signals, but i'm using lcd tv with scart cable.

     

    Component RGB is much more common in the US. Would you expect that it would work with it?

     

    -Larry

  11. Hi bfk2+-

     

    I'm certainly interested. FWIW, your errors sound reminiscent of termination issues that I can remember from long ago.

     

    I finally got around to running drac030's RWTEST.COM using my MIO 1.4b3 + ST157N, and it returned (apx) 6300 B/sec READING and 6500 B/sec WRITING. I previously could tell it was a little slow, but just how slow was a surprise.

     

    I've ordered another 50-pin drive - a more modern Seagate Hawk-2, ST31230N. So I'll see how that goes. If this drive works and is still slow, then I'm going to attempt to duplicate warerat's setup -- drive, termination power, etc.

     

    Did you ever get your ST157N reformatted with 512-byte sectors?

     

    -Larry

  12. I wonder if there is need for another production run of VBXE graphics adapter for 8 bit atari

    Although names says XE it can be used in any atari having ANTIC/GTIA and FREDDY chips on board

    for FREDDY-less machines clock divider must me used

    (snip...)

    prototype should be ready till 25 of april, and production run should start by the end of april

    cost of ready board is not know yet, but should be under $100 (this is rought estimate, more exact price should be know till 25 of april)

     

    If it will work with NTSC, and around $100 -- I'm in.

     

    -Larry

  13. Recently giving my 1050s some nice refurb treatment, cleaning, lubing, etc. I was taking note of the capacitors as I know those are most likely to die as the drives age. None of my drives has any problems, and all seem to have ELNA brand capacitors. I noticed the caps that needed replacing in this case weren't ELNA but Richey brand. ELNA's website trumpets their reliability, so I was wondering if there was a trend with bad caps.

     

    Anybody who's had to recap 1050s (or others), what kind of capacitors were they (if you know)?

     

    Very nice photos!

  14. That should work. Any reason however, that you don't want to change the scsi ID of the drive?

     

    No, didn't think I'd need to.

     

    But as I think more about it, changing the ID's might be good "insurance" that I don't write to the wrong drive, since the MIO writes data inverted as compared to the way my BB is set up.

     

    -Larry

  15. Yes, SCSI chains always need to be terminated on *each* end. Are you planning on wiring both BB and MIO to the same chain at the same time? Typically the controller card does it own auto termination, some even supply power down the scsi chain. Also, both scsi controllers would be using the same scsi ID. It is possible if only one controller is powered on at a time it *may* work w/o damaging anything, but I wouldn't recommend it. If you wanted to swap the cable between controllers with only one drive on at a time, what you stated will work.

     

     

    I was thinking of the following:

     

    MIO *OR* BB-------------------------------------HDD1-----------HDD2 (T)

     

    (HDD2 would be terminated; HDD1 would not)

     

    Only one controller would be attached to the I/O cable at one time -- physical isolation by swapping the controller, but "flip the power switch" to activate the other drive.

     

    -Larry

  16. I'm thinking about trying to put two drives in my "shoebox" case -- one for the Black Box and one for the MIO. I would have separate power switches for each drive, but use only one ribbon cable. Since both drives would never be powered at the same time, I presume they could have the same SCSI ID numbers without interfering with each other? What about the termination -- would it still only be at the end of the chain?

     

    -Larry

  17. Most impressive! That's great news!

     

    So I've been doing two things today-- hashing away at the MIO firmware and trying to nail down what the reliability problem is for those of you that have drives that kind of work. I think I found it.

     

    All of the sudden, the MIO isn't a slouch anymore. This is with the unreleased 1.4b3 firmware, using RWTEST.COM with SDX 4.42. Ramdisk results done with SpartaDOS 3.2d. Drive is Seagate ST118273LC.

     

    (snip...)

  18. In looking through various Seagate drive descriptions (both on eBay and the Seagate web site) I find "suffixes" of

     

    WC -- W means "Wide?" as in 80-pin?

     

    WC -- What does C mean? I can't find a "dictionary" of Seagate descriptors.

     

    How are 68-pin drives differentiated?

     

    Anyone?

     

    -Larry

  19. With the adaptec adapters to MFM and RLL mentioned in the manual, every drive I tried worked... and I tried some real odd balls as they were all I could afford to keep for myself at the time (vs. selling to other people).

     

    Hi Slore-

     

    Yes, the Adaptec solution works great if you have or can find the older MFM/RLL hardware.

     

    But I'm referring to firmware 1.4xx with 512 bytes/sector *and* newer embedded SCSI drives. (OK, the ST157N is borderline, but I still had one from my ST days, and it works great with 1.4xx.)

     

    BTW, are you indicating that 1.4xx works with an Adaptec/MFM drive with 512 bytes/sector? Although I'm not sure why you would want to do that -- 1.4xx is somewhat slower than 1.1.

     

    -Larry

×
×
  • Create New...