|
Peter_in_2780 wrote: If the machine is that old, it may very well have PATA/IDE disks, not SATA.
I still have a working USB 1.0 case from 2004 / 2005.
The 32 GB HDD inside (an old seagate) is still working 
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
I still have my old Dell Pentium-something tower that came with Windows ME (ptui ptui ptui). Late 2000.
Installing XP when it appeared the next year was a lifesaver.
Under a hundred gigs of 5.25 HDD, 3.5 and 5.25 floppies, CD...
I think I stretched the RAM to 256MB.
I upgraded the dialup modem to 56kbps.
Ah, the good old days....
Software rusts. Simon Stephenson, ca 1994. So does this signature. me, 2012
|
|
|
|
|
thanks for the link!
diligent hands rule....
|
|
|
|
|
I agree, what could possibly be relevant after 20 years?
Unless games for a retro build?
The less you need, the more you have.
Why is there a "Highway to Hell" and only a "Stairway to Heaven"? A prediction of the expected traffic load?
JaxCoder.com
|
|
|
|
|
Mike Hankey wrote: I agree, what could possibly be relevant after 20 years?
I saved the data of my father-in-law after an issue with an indian call center with an aprox. 12 years old 32 Bit version of FileScavenger.
Some old tools are priceless.
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Awesome, definitely worth salvaging.
Good luck
The less you need, the more you have.
Why is there a "Highway to Hell" and only a "Stairway to Heaven"? A prediction of the expected traffic load?
JaxCoder.com
|
|
|
|
|
you are right: games
diligent hands rule....
|
|
|
|
|
I don't know if it related to your issue. But i had an HP Pavillion Laptop from 2005 who started to have strange behavior . He started to not power on everytime , sometimes it powered up , then the last day not , i had to wait few days and it powered up. The delay between the time i was able to power it increased with time until the moment it never power up again.
I thought it was a problem with my power button. I bring the laptop to repair . And the guy check and say me nothing seemed to be wrong with power supply or button. But he just clear a persistant ram and the PC worked again.
I got back the PC and it worked normally for 2 weeks.. and then started to have the same problem...
And at that moment , i just thought about planned obsolescence.
what i did , when i was able to start the PC , i went directly in the BIOS and changed the date . I went 10 years back. We were in 2016 , i set the date backto 2006.
And after that , the PC worked again normally. The problem never occurs again.
the PC worked till 2019 where it died but due to the graphic card.
|
|
|
|
|
Southmountain wrote: 2002. Now I get some time to work on this PC
  that's ... 20 years ago.
|
|
|
|
|
Odds are it is the power supply.
Back around that time, there was a company out of Taiwan that made the majority of the capacitors used in PC equipment (I can't remember the name off hand). These capacitors had a life expectancy of about 5 years before they would swell and blow the top into a dome-like shape. Viewsonic was one of the companies that got nailed by this problem and actually sold a repair kit to replace the capacitors in many of their displays.
You might "borrow" a power supply from some other piece of equipment and see if that makes a difference.
|
|
|
|
|
In addition to the PSU, there are capacitors on the mother board that go bad. The ones you want to look at are clustered around the PSU plug. They are typically about 10,000 mfd. If the top of the capacitor cases are rounded, that means they need to be replaced. I've had to replace them in several P4 computers. It didn't fix the problem in the last computer I tried to fix, so months later when I was planning on scrapping the computer, I powered it up for a last test. It has been running perfectly since! Don't use the computer for much as it has Windows 2000 Server installed, but I was able to back up the [probably useless] data.
|
|
|
|
|
Electrolytic capacitors have a finite lifespan so the first thing I'd check is the power supply.
|
|
|
|
|
|
|
Sorry, I have to go with this one.
Iron Maiden - Seventh Son of a Seventh Son - YouTube[^]
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
I don't see a forum for SC/Git, so if there is let me knnow and I'll move this.
Using VS2019. I accidentally had a large ZIP file in my project folder. When I attempted to push to remote Git failed with "Large file detected".
Now I'm stuck. I deleted the large file, but the commit still shows it. There doesn't seem to be a way to remove it from the commit. I've tried Revert multiple times and that seems to have no effect. I tried a test commit and a test pust. I now seee 4 outgoing commits, including my tests and the original with the ZIP file in it.
I've Googled for the last hour and can't find anyway to undo these commits. The original commit really doesn't have much in it, and I made a backup.
How do I remove the 4 outgoing commits??? There HAS to be a way to undo this mess!!
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
|
|
|
|
|
|
Chris Losinger wrote: git reflog
What??
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
|
|
|
|
|
I tried command line git commads and I get back 'Git not found'. Git is installed and the paths to it are in my environmental variables
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
|
|
|
|
|
This will rollback the last 4 commits back to the staging area (from committed to staged):
git reset --soft HEAD~4
This will rollback the last 4 commits back to the working tree (from committed to unstaged):
git reset --mixed HEAD~4
You could also use --hard if you wanted to just nuke everything back to a point (you'd lose the files rolled back though). Luckily it seems like the problem is still local, so reset should be safe from the perspective of the remote's history.
git revert probably didn't do what you wanted because it doesn't "rollback" in the traditional sense. It creates a new commit that reverts the specified commit but does not alter the history. So if the problem is a file in a commit that's causing an error, that file will still be in the history, still causing the problem.
Here's some reading for further options to check out:
Git - Undoing changes | Atlassian Git Tutorial
|
|
|
|
|
I tried command line git commads and I get back 'Git not found'. Git is installed and the paths to it are in my environmental variables
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
|
|
|
|
|
Other than suggesting re-installing it, I'm not really sure what I could do to help with that. I don't know your system, configuration, etc.
|
|
|
|
|
in visual studio 2019, you need to go to "view --> manage git branches" right click the last good commit and select revert -> hard delete. this will delete/remove all commits "above/after" the one you selected. see instructions below. I think they describe the process more accurately.
I am not looking at visual studio right now, so I may have some of the label text wrong but the actions are correct.
The Git experience in Visual Studio 2019 | Microsoft Docs[^]
I have to do this every so often myself. fairly simple process.
I don't muck around with git commands, but some of my friends do. you can do this process either way: gui or command line.
also, you really need to comment your commits well, if you are not doing this. they help identify your commits better. you can always right click a commit in the list and view commit details to be sure.
|
|
|
|
|
Slacker007 wrote: In visual studio 2019, you need to go to "view --> manage git branches" right click the last good commit and select revert -> hard delete. this will delete/remove all commits "above/after" the one you selected.
I have tried this multiple times and it seems to have no effect. All commits are still there... except now the Revert link is disabled for the last good commit. The commit(s) I'm trying to get rid of are still there and when I push, the all are pushed - which errors out
See this pic
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
|
|
|
|
|
Thanks for the pic. It actually helps.
Yeah, that is both interesting, and frustrating for you, I am sure. I am not entirely sure why this is not working for you.
It is not ideal, but you could copy your current local repo to a temp folder and then create a new branch off of master and copy over your current changes (in the temp folder) and commit and push.
then just delete the "bad/difficult" branch once you successfully pushed your changes to the server and merged to master.
I have done this a couple times in the past and it works. Again, not ideal, but it works.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
