brianc@cognos.uucp (Brian Campbell) (08/19/87)
Has anyone else had any problems with the 1.2 posting of xt_wini.c? It now works for my hard drive (Seagate 225 with WD controller), but I had to swap the drive type calculations in init_params(). Is the posting wrong, or are my jumpers somehow backwards? -- Brian Campbell uucp: decvax!utzoo!dciem!nrcaer!cognos!brianc Cognos Incorporated mail: 3755 Riverside Drive, Ottawa, Ontario, K1G 3N3 (613) 738-1440 fido: sysop@163/8
sullivan@marge.math.binghamton.edu (fred sullivan) (08/23/87)
In article <1288@cognos.UUCP> brianc@cognos.uucp (Brian Campbell) writes: > > Has anyone else had any problems with the 1.2 posting of xt_wini.c? >It now works for my hard drive (Seagate 225 with WD controller), but I >had to swap the drive type calculations in init_params(). Is the >posting wrong, or are my jumpers somehow backwards? It worked just fine with mine (same drive, WD controller). Fred Sullivan Department of Mathematical Sciences State University of New York at Binghamton Binghamton, New York 13903 Email: sullivan@marge.math.binghamton.edu
butler@brl-smoke.ARPA (Lee A Butler ) (08/24/87)
In article <1288@cognos.UUCP>, brianc@cognos.uucp (Brian Campbell) writes: > > Has anyone else had any problems with the 1.2 posting of xt_wini.c? I too can now use my hard disk, but occaisonally get errors/problems. I haven't taken time to figure it out yet. Hmmm. -- Lee A. Butler butler@stsci.arpa | butler@brl.arpa Space Telescope Science Institute Usenet: {noao,nrao1}!stsci!butler 3700 San Martin Drive SPAN: SCIVAX::BUTLER (6405::BUTLER) Baltimore, MD 21218 Phone: (301) 338-4531
allbery@ncoast.UUCP (Brandon Allbery) (08/26/87)
As quoted from <1288@cognos.UUCP> by brianc@cognos.uucp (Brian Campbell): +--------------- | Has anyone else had any problems with the 1.2 posting of xt_wini.c? | It now works for my hard drive (Seagate 225 with WD controller), but I | had to swap the drive type calculations in init_params(). Is the | posting wrong, or are my jumpers somehow backwards? +--------------- I had this happen also. I don't know what having write precomp turn on too early does, but check for that as well; I discovered that it was using a value of 128, while my ST225 data sheet says 256. (This is the starting cylinder for write precomp.) I added a line to change it in the wini.c I compiled into Minix. -- Brandon S. Allbery, moderator of comp.sources.misc {{harvard,mit-eddie}!necntc,well!hoptoad,sun!mandrill!hal}!ncoast!allbery ARPA: necntc!ncoast!allbery@harvard.harvard.edu Fido: 157/502 MCI: BALLBERY <<ncoast Public Access UNIX: +1 216 781 6201 24hrs. 300/1200/2400 baud>> ** Site "cwruecmp" has changed its name to "mandrill". Please re-address ** *** all mail to ncoast to pass through "mandrill" instead of "cwruecmp". ***
ritchie@hplsdla.HP.COM (Dave Ritchie) (08/31/87)
>/ allbery@ncoast.UUCP (Brandon Allbery) writes: >As quoted from <1288@cognos.UUCP> by brianc@cognos.uucp (Brian Campbell): >+--------------- >| Has anyone else had any problems with the 1.2 posting of xt_wini.c? >| It now works for my hard drive (Seagate 225 with WD controller), but I >| had to swap the drive type calculations in init_params(). Is the >| posting wrong, or are my jumpers somehow backwards? >+--------------- > >I had this happen also. I don't know what having write precomp turn on too >early does, but check for that as well; I discovered that it was using a >value of 128, while my ST225 data sheet says 256. (This is the starting >cylinder for write precomp.) I added a line to change it in the wini.c >I compiled into Minix. Try again.... write precomp starts at cylinder 300, not at 256, according to the ST225 manual I have for the ST225 on my Ampro. Dave Ritchie hplabs!hp-lsd!ritchie
mlinar@poisson.usc.edu (Mitch Mlinar) (09/09/87)
In article <5890003@hplsdla.HP.COM> ritchie@hplsdla.HP.COM (Dave Ritchie) writes: >>/ allbery@ncoast.UUCP (Brandon Allbery) writes: >>As quoted from <1288@cognos.UUCP> by brianc@cognos.uucp (Brian Campbell): >>+--------------- >>| Has anyone else had any problems with the 1.2 posting of xt_wini.c? >>| It now works for my hard drive (Seagate 225 with WD controller), but I >>| had to swap the drive type calculations in init_params(). Is the >>| posting wrong, or are my jumpers somehow backwards? >>+--------------- >> >>I had this happen also. I don't know what having write precomp turn on too >>early does, but check for that as well; I discovered that it was using a >>value of 128, while my ST225 data sheet says 256. (This is the starting >>cylinder for write precomp.) I added a line to change it in the wini.c >>I compiled into Minix. > > Try again.... write precomp starts at cylinder 300, not at 256, according >to the ST225 manual I have for the ST225 on my Ampro. All those numbers regarding write precomp are also fairly meaningless. As a site tester for well over 80 different types of hard drives (whew!), I can state with some certainty that write precomp on MODERN drives (>1983) has little effect on the drive data read/write capability. During tests, the write precomp was moved from cyl 0 all the way to the last cyl. What we found was that write precomp within 50% of the quoted nominal value has no effect on data integrity. When in doubt, set your write precomp to 128 (which is true in all but a few drives). Regardless of what the manufacturer said, this value always worked, although if you know the suggested value, use it. Regarding the ST225, setting at 128 is at the envelope edge, but still ok. The difference between 300 and 256 is not worth mentioning. HOWEVER, what IS worth mentioning is that once you pick a value and FORMAT your drive that way, STAY with that value. The soft error with time increases very slightly if you moved outside the FORMAT setting by 30%. If memory serves correctly, the IBM rounds off to the nearest power of 2 (e.g. either 128 or 256) in its tables. (Some controllers round off to the nearest 64 or 128.) Hope this helps somebody. -Mitch
allbery@ncoast.UUCP (Brandon Allbery) (09/12/87)
As quoted from <5890003@hplsdla.HP.COM> by ritchie@hplsdla.HP.COM (Dave Ritchie): +--------------- | >I had this happen also. I don't know what having write precomp turn on too | >early does, but check for that as well; I discovered that it was using a | >value of 128, while my ST225 data sheet says 256. (This is the starting | >cylinder for write precomp.) I added a line to change it in the wini.c | >I compiled into Minix. | | Try again.... write precomp starts at cylinder 300, not at 256, according | to the ST225 manual I have for the ST225 on my Ampro. +--------------- The test sheet that came with my ST225 (shows results of factory tests) shows at the top: DATA DATA WRITE REDUCE PARK STEP HEADS CYLS PRECOMP WRT CUR CYL PULSE CYLS CYLS RANGE ------------------------------------------------ 4 0-614 256-614 N/A 670 5-200 US I can say no more about it; the tech spec sheet doesn't talk about write precomp as far as I can see. -- Brandon S. Allbery, moderator of comp.sources.misc {{harvard,mit-eddie}!necntc,well!hoptoad,sun!mandrill!hal}!ncoast!allbery ARPA: necntc!ncoast!allbery@harvard.harvard.edu Fido: 157/502 MCI: BALLBERY <<ncoast Public Access UNIX: +1 216 781 6201 24hrs. 300/1200/2400 baud>> All opinions in this message are random characters produced when my cat jumped (-: up onto the keyboard of my PC. :-)