I do not believe it.
-
I managed to get this stupid win 8.1 lappie into recovery mode. How? The obvious way. Plug in a VGA monitor lead and turn the power on. No, seriously. That's what I did, and Windows immediately came up with "Had a problem starting, what do you want to do?" On the lappie screen, of course, not the VGA connected monitor - that stayed blank. And although windows couldn't fix the start up problem it is at least "refreshing" the PC - which is a reinstall of Win8 without scrubbing the HDD, it seems: you have to reinstall every app after that, but keep your data. I'll do a disk image when it's powered up ok, and before I install anything. My dislike for Win8.x grows with every single exposure...
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
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!
-
I managed to get this stupid win 8.1 lappie into recovery mode. How? The obvious way. Plug in a VGA monitor lead and turn the power on. No, seriously. That's what I did, and Windows immediately came up with "Had a problem starting, what do you want to do?" On the lappie screen, of course, not the VGA connected monitor - that stayed blank. And although windows couldn't fix the start up problem it is at least "refreshing" the PC - which is a reinstall of Win8 without scrubbing the HDD, it seems: you have to reinstall every app after that, but keep your data. I'll do a disk image when it's powered up ok, and before I install anything. My dislike for Win8.x grows with every single exposure...
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
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???
-
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!
-
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! :laugh:
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
-
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! :laugh:
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
What lappie is it?
Wrong is evil and must be defeated. - Jeff Ello
-
What lappie is it?
Wrong is evil and must be defeated. - Jeff Ello
Acer E1-571
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
-
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 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, 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.
-
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.
-
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.
