Subj : Re: Miss.RvrDamBreach-Davenpt To : Barry Martin From : Nancy Backus Date : Fri Oct 04 2019 17:36:26 -=> Quoting Barry Martin to Nancy Backus on 22-Sep-2019 09:40 <=- NB>>> Exactly... a week in June, 2 different weeks in July, almost a NB>>> week in August, and now a long weekend in September... And coming NB>>> up, about a week at the end of September, and another long NB>>> weekend in October... Definitely multiple.... BM>> We'll be here! NB>> Waiting patiently... ;) BM> Well, I'l be doing something to occupy the time but won't post a WHERE BM> ARE YOU?!! Good thing, as all the trips have made me quite erratic in posting... ;) I'm seeing the light at the end of the tunnel, I think... my son's return flight to Turkey is on the 22nd, so that will be one last trip for the year... getting him back to the Montreal Airport... We'll close the camp for the winter just before I take him to the airport... :) BM>> I'm still surprised I haven't used more RAM on the various computers BM>> up here with the various functions. The Backend for MythTV does a form BM>> of video transcoding and that "takes room" to do some place. This BM>> system (the one I'm one currently) I have multiple windows open BM>> concurrently and it is only using 5.9 GB. ...As long as everyone's BM>> happy! NB>> Only. 5.9GB sounds like an awful lot to me.... ;) NB>> Especially as I have but a small fraction of that... :) BM> True: everything is relative. Think I told you or you may have read BM> where my first IBM-compatible computer had a 20 MB hard drive -- BM> thought it would take forever to fill, especially as in the BM> flipping-floppies mindset from my first computer. So nine months later BM> running low on space, the sister computer becomes available (customer BM> return because he or she totally screwed up the OS so the department BM> manager sells to me for cheap) -- 40 MB hard drive. I eventually BM> network together for a combined 60 MB -- I'll _never_ run out of room! BM> ...Uh-huh! A very common story... NB>>>> Maybe you should suggest that to him.... or do the actual work NB>>>> with an iteration of the program, not the original one...? BM>>> I'll have to look to see how the executable files I was working with BM>>> were done -- IIRC most are on Backend 2 and that was shut down. Seems BM>>> easy enough to create a master configuration file; the trick is to BM>>> have the script file look at it and pull the information! NB>>> So now you just have to figure out how to make that work... :) BM>> And learn Python and other programming stuff..... NB>> Keeps your brain limber and flexible (as long as it doesn't totally NB>> overwhelm [g]).... BM> Right now I'd have to have a need other than 'handy to know'. BM> Admittedly a lot of my recent learning tends to be knee-jerk: this BM> isn't working, error code is , find what that means, etc. BM> And I really have no need to do programming -- well, in-depth, do do BM> some 'lite' stuff with the occasional scripting, but that's more BM> cookbook: patch in bits and pieces. Is more time consuming than if I BM> knew how to do from properly learning but.... Maybe someday when you are caught up on all those projects, and no But Firsts get in the way.... Maybe even take a course at the community college, or online...? :) BM> (Was reading a reply from the developer of NCID to a question someone BM> else posted. Gave the answer and a bit of pertinent side-information BM> which also mentioned he hadn't expanded NCID to do because he BM> had no interest to do so. I can relate!) Only so much one can do at a time... :) And it helps to be interested in what one is doing, especially when one is free-lancing... ;) BM>>>> LIS I think he's one of the developers though never stated anywhere BM>>>> and didn't make any difference - he knew the stuff was what mattered. NB>>>> Yup, either way, he's developing it now, too... and knows what's NB>>>> going on with it... ;) BM>>> Or at least the 'transfer utility' portion of it. ...Now getting more BM>>> curious as to how it's all done! While I was working with him I was BM>>> more interested in reporting the results, detailing what went wrong so BM>>> he could correct -- basically I was his eyes and there were more than a BM>>> few times "something's wrong" but I didn't know exactly what to report BM>>> to give the information on how to fix so he got too much information. NB>>> So understanding it might make reporting bugs better/easier.... :) BM>> True - I'd probably know better what was expected so would be able to BM>> narrow down the error information. NB>> Or at least be able to use the right jargon correctly... ;) BM> That would be helpful! A reason to consider the whole idea more strongly... :) NB>>>> Eventually... ;) BM>>> In the mean time..... NB>>> Other things pop up and need doing.... :) BM>> Right. Pulled an older computer from 'storage'; had been set aside BM>> because I couldn't get the DVD drive to work. Well, the drive worked BM>> fine just not in that computer. ...Was considering using the computer BM>> as a Frontend in the TV Room in the basement. Not going to work as BM>> the motherboard is old and slow, so pulled that and should have a BM>> replacement delivered today or tomorrow. NB>> Always something happening... ;) BM> Keeps me busy and in mischief! ...Wait: did I type that right?! Probably... BM>> I think the largest file I've played with was 5-point-something BM>> gigabytes. No problems until got to a little over 4 GB and the BM>> filesystem on the thumbdrive truncated. (reformmated the thumbdrive BM>> to a different filesystem and was fine.) NB>> Totally mind-boggling to me... I think I'll just avoid the huge NB>> files and stay happily in my old small system... ;) BM> Probably 95% of my files are the usual handful of megabytes; the BM> over-4GB ones are recordings of TV shows and normally I don't have a BM> thing to do with them other than select which one to play and the BM> computers handle the rest. Manual copying is rare, with the exception BM> of the Transfer Project. Still mind-boggling to me... ;) BM>>> Yes. :) Could have changed the PSU and HDD-->SSD in one step but BM>>> prefer to do major (and sometimes minor) changes in steps -- just BM>>> easier troubleshooting should something go wrong. NB>>> Possibly easier to backpedal if needed to that way, too... BM>> For me, yes. I know a lot but there are gaping holes in what I do BM>> know, so sometimes an obvious issue to others is a mystery to me, BM>> while other details I can keep right up. NB>> Most things are a mystery to me... ;) BM> All depends on what one needs to/wants to know. I have little BM> interest in working on cars as in changing oil or even swapping out the BM> battery. Others like to and I'm glad do so I can have them do the stuff BM> I don't care to. Well, I was talking more about computers and the like, but that's another area that applies... ;) In previous times, I've been known to change my own oil (only did it once and decided it wasn't a job I cared to do again)... and other simple changeouts... but I'm happy to take the car to our mechanics now... :) BM> As sort of a follow-up the external fan fixed the problem. Not BM> elegantly. Hindsight may have been repairable: took the fan guard off BM> and the blades almost fell out ==> seems like they had just glued the BM> fan blade assembly to the motor shaft. Not sure if could have glued BM> and reassembled but part of the frame inside was loose -- not sure if BM> that was from unscrewing the fan guard or another problem. By the time BM> I thought of maybe glueing I had snipped the positive lead to the BM> original fan's motor. New 120mm fan over where the fan guard was -- do BM> a test run -- seems fine! It works now... that's the important thing... ;) Sometimes figuring out what someone else was thinking when they put things together is more effort than just replacing things... ;) ttyl neb .... Procrasinators Anonymous Meeting tomorrow. Or day after... --- EzyBlueWave V3.00 01FB001F * Origin: Tiny's BBS - http://www.tinysbbs.com (454:1/452) .