Subj : Miss.RvrDamBreach-Davenpt To : Nancy Backus From : Barry Martin Date : Sun Sep 22 2019 09:40:00 Hi Nancy! BM>> True, as multiple. 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... ;) Well, I'l be doing something to occupy the time but won't post a WHERE ARE YOU?!! NB>>> overwhelm this computer with a huge packet... It needs more than NB>>> double (maybe triple?) the space to open it, and more headspace NB>>> to close it again... And I tend to not really have a lot of room NB>>> available at a time... BM>> Right. I vaguely recall there is a time when there are two files in BM>> memory, before gets written to a temp file on the hard drive. NB>> Yup, something like that... BM> I'm still surprised I haven't used more RAM on the various computers BM> up here with the variuos 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... :) True: everything is relative. Think I told you or you may have read where my first IBM-compatible computer had a 20 MB hard drive -- thought it would take forever to fill, especially as in the flipping-floppies mindset from my first computer. So nine months later running low on space, the sister computer becomes available (customer return because he or she totally screwed up the OS so the department manager sells to me for cheap) -- 40 MB hard drive. I eventually network together for a combined 60 MB -- I'll _never_ run out of room! ...Uh-huh! NB>>>> One-function utilities aren't all that bad a thing... as long as NB>>>> they perform a function that you need to have done.... :) BM>>> Yes, though for this utility it would seem to make more sense to have BM>>> a configuration while the user would edit instead of editing the actual BM>>> programme file. Essentially the same as the configuration file BM>>> modifies the programme file, just I prefer not fiddling with the BM>>> master. 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 NB> totally overwhelm [g]).... Right now I'd have to have a need other than 'handy to know'. Admittedly a lot of my recent learning tends to be knee-jerk: this isn't working, error code is , find what that means, etc. And I really have no need to do programming -- well, in-depth, do do some 'lite' stuff with the occasional scripting, but that's more cookbook: patch in bits and pieces. Is more time consuming than if I knew how to do from properly learning but.... (Was reading a reply from the developer of NCID to a question someone else posted. Gave the answer and a bit of pertinent side-information which also mentioned he hadn't expanded NCID to do because he had no interest to do so. I can relate!) 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... ;) That would be helpful! BM>>> BTW, the transferred files (from old system to new) work fine. The BM>>> old Backend has been powered off for some time -- maybe only a week but BM>>> seems longer! Still have to move the hardware around -- the new BM>>> Backend is still on the floor and needs to be moved to the cabinet, but BM>>> first need to make room on/in the cabinet.... 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... ;) Keeps me busy and in mischief! ...Wait: did I type that right?! NB>>> You have WAY more capacity than I have... ;) But the important NB>>> thing is that you do have what you need to do the job at hand... :) BM>> And DOS won't handle that amount anyway. Well, could partition a BM>> multi-terabyte drive. Don't think that would even work because of the BM>> filesystem. NB>> Might be driven over to linux... or have a zillion partitions, NB>> and still not be able to handle large files... ;) 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... ;) Probably 95% of my files are the usual handful of megabytes; the over-4GB ones are recordings of TV shows and normally I don't have a thing to do with them other than select which one to play and the computers handle the rest. Manual copying is rare, with the exception of the Transfer Project. NB>>> All right... :) Nice when things work properly... :) 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... ;) All depends on what one needs to/wants to know. I have little interest in working on cars as in changing oil or even swapping out the battery. Others like to and I'm glad do so I can have them do the stuff I don't care to. BM>>> Will see about replacing the fan in the old PSU instead of buying a BM>>> whole new PSU. NB>>> Makes sense... and with it out of the computer, twill be easier NB>>> to work with... ;) BM>> Definitely, especially as I think the screws to open the PSU were BM>> underneath! ...Will have to see what the price of a replacement BM>> fan is: with another computer it's greatly cheaper to replace the CPU BM>> fan/heatsink assembly than buy the replacement fan (!). NB>> That does happen from time to time.... :) BM> The Scottish Guy in me doesn't understand things like that! NB> It's the way modern economics works, is all... As sort of a follow-up the external fan fixed the problem. Not elegantly. Hindsight may have been repairable: took the fan guard off and the blades almost fell out ==> seems like they had just glued the fan blade assembly to the motor shaft. Not sure if could have glued and reassembled but part of the frame inside was loose -- not sure if that was from unscrewing the fan guard or another problem. By the time I thought of maybe glueing I had snipped the positive lead to the original fan's motor. New 120mm fan over where the fan guard was -- do a test run -- seems fine! ¯ ® ¯ Barry_Martin_3@ ® ¯ @Q.COM ® ¯ ® .... Redneck: If you come back from the dump with more than you took --- MultiMail/Win32 v0.47 þ wcECHO 4.2 ÷ ILink: The Safe BBS þ Bettendorf, IA --- QScan/PCB v1.20a / 01-0462 * Origin: ILink: CFBBS | cfbbs.no-ip.com | 856-933-7096 (454:1/1) .