|
Deja Vista
New version: WinHeist Version 2.1.1 new web site.
I know the voices in my head are not real but damn they come up with some good ideas!
|
|
|
|
|
|
No Vista is much better and less buggy than Win8
|
|
|
|
|
Yeah, At least the start menu opens on Vista. And it wasn't actually too bad once they patched the thing up, it's name was just stained forever due to it being a complete flop on launch.
In windows 8.1/10 TP I find that pressing the start menu button sometimes leaves the desire for the start menu to actually open.
|
|
|
|
|
I can't even get the latest build to work on a VM
|
|
|
|
|
Yeah, I managed to get one of the older builds to install into a KVM machine on a linux host under libvirt, but not managed to get it to update as it blue screens. Fairly sure it was something about an unhanded system thread exception.
If you google the BSOD message and google it there was an article somewhere which helped me but I can't find it again. It was to enable a certain CPU instruction inside virtual box which is disabled by default, I'm away from home at the moment at last I checked the power was out so I can't SSH in and try to find what I enabled, enabling it solved the issue but I couldn't figure out how to do it elsewhere.
|
|
|
|
|
I'm trying it in a 2 year old version of VM Ware Player, on a Vista Host.
If I have time I may just drop it on some extra hardware that I have around here and see.
So far what I was able to see it is not anything I would be interested in using besides testing.
|
|
|
|
|
After too many times losing my data I have come to format a system partition and a data partition on all my machines.
Then when I need to do a fresh install I reformat the system partition, install the new OS along with all the applications onto the system partition and the data is still there.
Once you lose your pride the rest is easy.
In the end, only three things matter: how much you loved, how gently you lived, and how gracefully you let go of things not meant for you. – Buddha
|
|
|
|
|
I went through this recently with this wife's all-in-one 8.1 system. Funny how this process used to be easier...usually F8, and you had a few seconds to hit it. Now it seems that the PC only allows access to those options when 'it' decides there is a problem. I imagine with the reinstall, you'll have lots of updates, but at least they shouldn't need to be downloaded. Sounds like you're on the road to recovery!
"Go forth into the source" - Neal Morse
|
|
|
|
|
F8 only works at a specific stage in the boot process, only optimizations in the whole boot process and everything else leaves you like a slither of a second to hit F8 at the right time, it still works, providing you can get in there in time.
There was a way to get to it if you managed to boot to a login screen, fairly sure it was either ctrl or shift, holding that and hitting restart would take you to the boot options, but widely useless if you can't even get that far, your left praying the successful boot flag isn't marked due to how far it manages to get before it topples itself.
|
|
|
|
|
Yeah, the boot is now so fast that you have to select shutdown and start with the boot menu option instead of having the system wait to give you that option every time you boot.
|
|
|
|
|
Andy Brummer wrote: every time you boot.
I would rather give W8 the boot.
Marc
|
|
|
|
|
I had an old Windows 7 system that finally became impossible to repair inexpensively to make it worth it, so I bought another WinTel system, and got stuck with 8.1 (and as I was in a foreign country, also not in my native language, English.) I did a complete rebuild with 7 (which required me to do a repartition via Linux on a stick drive!) from a stick that I had an earlier download for the LAST time I had to do a rebuild (on that old system.)
I also have an ASUS Transformer running 8.1 that I use to read books, listen to music or watch movies - and to act as an emergency system (like when I had to buy & rebuild that aformentioned system) - or to access the web to get some quick information when I am away from my place. I really like it for doing those non-emergency things, but because I have a penchant for having a zillion tabs open in the browser, I was finding that when used in its emergency role, it was crashing about every 10 minutes; it's a good thing that it reboots really quick!
|
|
|
|
|
If I hold down the bios or boot selection keys on my keyboard before powering on, I get right to the respective screens.
Did you try that?
What do you get when you cross a joke with a rhetorical question?
The metaphorical solid rear-end expulsions have impacted the metaphorical motorized bladed rotating air movement mechanism.
Do questions with multiple question marks annoy you???
|
|
|
|
|
Oh yes. F2, both INS keys, both DEL keys, complete with all combinations of SHIFT, CTRL, and ALT.
Searched Google several times, swore lots, you know the kind of thing.
It seems to be UEFI related: it's not a "bios" per se in reality so it behaves very differently.
Bring back EPROM bioses, that's what I say! 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
|
Acer E1-571
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Hi CP community.
We hired a guy that did this a while ago. It annoyed me then, and now I have a project that I'm refactoring that lo and behold has it as well.
Maybe I'm missing some recommended practice (I googled it), and I don't mean to start a war or anything. I just don't see an obvious use for things like this. The message is the same when a socket error occurs...
try
{
DoSomething();
}
catch (SocketException e)
{
Console.WriteLine(e.Message);
conn.connecting = false;
}
catch (Exception e)
{
Console.WriteLine(e.Message);
conn.connecting = false;
}
What purpose in life, universe, code, etc... does a practice like this serve?!
(Clarification for all of those who've been giving concrete reasons for catching different exception types. I get that. I do that as well.
I'm saying that the guy we hired previously would handle several exception types only to do the same thing as the catch-all block. Literally the same thing. Sometimes he would catch a type only to throw it to the main block doing nothing with the specific type. It bugged the hell out of me.
Now I'm refactoring another project that is completely unrelated and I see a similar practice which made my mind wander to here...)
modified 20-Jun-15 14:01pm.
|
|
|
|
|
jeeves77 wrote: What purpose in life, universe, code, etc... does a practice like this serve?!
Zero
If the brain were so simple we could understand it, we would be so simple we couldn't. — Lyall Watson
|
|
|
|
|
Yes it has purpose. You should see this msdn article. [^]
But it wasn't utilized as suppose to.
modified 20-Jun-15 11:09am.
|
|
|
|
|
I looked, I saw: but I didn't see a purpose to having two exception catchers that do the same thing.
Yes, if the SocketException catcher logged it differently, or re-tried or similar, and the Exception catcher did a generic log-and-exit instead then it's would have a purpose.
But two exceptions (one of which catches everything) that do the same thing? I see no point, except to duplicate code and potentially cause a maintenance problem if the logging mechanism changes.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
We can't predict looking the above code since we don't know what Dosomething() method exactly do. What we can infer is that there is a socket processing behind since there is a catch exception on it.
|
|
|
|
|
It's irrelevant what DoSomething() does in regard to the catch-blocks. In case of an exception, either the first or the second catch block gets executed and they do exactly the same, so the more specific one is superfluous.
If the brain were so simple we could understand it, we would be so simple we couldn't. — Lyall Watson
|
|
|
|
|
They don't occur exactly with the same reason. Off course both catches exception but how each one will occur determine by the actual method logic. Suppose Dosomething() has DB process, then where you will think possible to be catched if error happens. On catch (Exception ex) block and where do you think the socket error will be catched on (SocketException sex). That is why the method logic determine the exception occurence.
|
|
|
|
|
It doesn't matter.
Regardless of what exception is thrown, the code executed will be identical. Which means that the separate catch for the "lesser" exception need not be there at all.
And if it needed be there, why put it in? All that does is leave a "hole" where duplicated code can become different over time and cause other problems - that's one of the advantages of inheritance: it removes the need to "copy and paste" code by reusing a single method in all derived classes. So if the method needs to be changed, it's in one single place instead of scattered all over the file and prone to being missed when the updates are done.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
