| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Re: Slicing |
1237c414e830 tech Hello Wayne - --8<--cut CA>> Hurts when you push a somewhat blunt object through your CA>> hand. WC> I can outgross that. Running a printing press improperly WC> cleaned by the night shift I was adjusting the web roller WC> guide when the allen wrench slipped out of the dry ink WC> filled adjustment allen screw. My hand dropped to the roll WC> stock running through the press at 540 Ft/Min., couple WC> hundred pounds of revolving mass and two 2 H.P. DC motors WC> came to a stop as my finger slid between the hard rubber WC> and stainless steel pinch rollers. My fingernail was driven WC> along the bone to just about the first joint where I WC> removed it with cheap loose pliers on something like the WC> fifth attempt to grasp the nail. Then I went to my WC> supervisior to get soome peroxide to pour over the wound. WC> This happened first thing in the morning and I finished the WC> day though it was a major owie when that finger touched the WC> frame of the press while adjusting various settings WC> throughout the day. I think that would've scared me so badly I would've had to go home and sleep it off. It's unfortunate how many of us were raised to be good soldiers and continue as though nothing has happened when we are badly injured. My first AMI was at work and I stayed there and finished my shift. Seems a bit insane to me now that I did that but the really weird thing is a younger man working next to me was having chest pains at the same time and he stayed and finished his shift too. We each deserve the same care and consideration we would show to our pets, our friends, and our family. It was a mistake to treat myself with such disregard. I would've never treated another living soul that badly. CA>> I don't do that anymore. ;-) WC> Me neither ;-) Someone less fortunate than I did the same WC> thing and it rendered his whole arm largely useless. To WC> this day I'll never know why the bone in the finger did not WC> crush resulting in that more serious outcome. Machinery is as unpredictable as the wind. There was a guy who was trying to set a land speed record at the Salt Flats. His car went out of control so he jumped out at over 200mph. No problem. Next year, same thing. Third year his car went out of control, he jumped and died. Life is like that. WC> OH yeah, this sytem I thought I'd fixed is evidencing WC> problems again and actually may never have stopped having WC> them but the problems of a hang or crash with Win 3.1 are WC> less severe than with Win 98 so I've managed to work around WC> it. Gotta try putting in a different hard drive ribbon WC> cable as that's free but fear it may be the H.P.'s on WC> motherboard board I/O :-( Those are about the only things WC> left it could be. Then again the Seagate drive I put in WC> there is ten years old... Two failed drives in a row? Glad WC> I kept the 6.4 Gig Quantum drive as it's possible it's good. If you can detail just what is happening to you and when (after a 'clean' boot with the machine turned off/on or 'other' etc.) something may click here. I did have random lockups here on my W31 for a long time but was never absolutely certain which change finally stopped that from happening. I began executing DR.WATSON at W31 startup, and made some changes to memory handling as I recall it. I replaced MSDOS v6 SMARTDRV.EXE, EMM386.EXE, HIMEM.SYS, and IFSHLP.SYS with newer versions from a W98SE version of MSDOS and I think that helped somewhat. You could try Microsoft's "Memory Valet" from: http://www.undercoverdesign.com/dosghost/dos/w31_cfg2.htm at the bottom of that page. It's a little-known free addon for W31 that Microsoft offered mainly to business users and there is a KB article link there that will explain what MEMVALET's intended use was. I _think_ that also contributed a great deal to my present more stable W31? I also added 'syshook.drv' (same webpage) that won't allow me to use ALL of the memory in the first meg as a 'saftey' precaution against out of memory errors. W31 must have a small amount of memory in order to use installed high memory even from the VM swap file. If it can't it will scramble the error messages (if any) and give wrong information about why it is crashing. Memory Valet and syshook.drv attempt to assist W31 in it's poor memory management practices. If you are using a permanent VM swap file, and you have to to use 32bit access, then once that gets scrambled W31 will continually reload, reuse, and re-crash. You have to reset to a temp VM, reboot, reset back to a permnanent VM swap file to erase the 'bad' VM information and start fresh. It's a pain but I recall needing to do that many times before stabilizing my setup. > > , , > o/ Charles.Angelich \o , > __o/ > / > USA, MI < \ __\__ ___ * ATP/16bit 2.31 * ... DOS the Ghost in the Machine! http://www.undercoverdesign.com/dosghost/ --- Maximus/2 3.01* Origin: COMM Port OS/2 juge.com 204.89.247.1 (281) 980-9671 (1:106/2000) SEEN-BY: 633/267 270 @PATH: 106/2000 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.