Tripredacus

One thing to consider about newer computers (I blame the OSes) is that they are not very accomodating to older people. I have been trying to find a replacement computer for and elderly friend of mine and have come up short. It basically comes down to he just can't read on the screen. Tablets and Smartphones are out because you can't change font size. So I figured we'll take a look at some Windows 8.1 notebooks at a retail store. Still can't read that either. No way to make the fonts bigger and Magnifier is clunky and confusing. You can't really change the video resolution to something smaller either. It seems there are no products available for the aging population who have degraded vision, who have relied for years on using Windows XP @ 800x600 with a 19" or greater display.

I know what you mean regarding the CPU. Yes that board is entirely capable of running 64bit code. When I first got it, I couldn't boot to WDS because all my PEs are 64bit. If you attempt to boot to WDS in this fashion, the boot rom is downloaded but the menu never appears and the system then proceeds to the next boot device. In order to use this board, we had to request a custom BIOS from ECS to allow us to boot x64 OS. However, using the stock BIOS, or the updated one from their website will result in a CPU architecture error if you try to boot say, Windows 7 x64 on a HDD. Something like "OS is 64bit but CPU is 32bit." That message comes from Windows itself, in a black screen similar to a BCD error. Regarding the floppy image part, this was what I meant by needing instructions. Tell me exactly what I need to look at and what software to use to do it and I can check for you.

I tested the ATIH2014P_6688_en-US.iso (burned to DVD) and it is able to boot in 32bit UEFI mode.

Google search results only provide a method of finding something. Certainly there are other ways to search for things, and certainly other repositories of information that are not indexed but can still be found through links or even the Wayback Machine. The idea that in court proceedings, you can ask for and be granted the ability to have relevant information removed from consideration of the case's outcome has always confused me.

As I've said before, the email provider has access to everyone's emails. They certainly are filtering spam, this is a given, but they already have said they are data mining emails. That's what this story is actually about, the fact this information was already made public and Google wants to get it stricken from the record. This works in the court of law but means nothing in the court of public opinion. It is very difficult to purposely remove something from the internet but that's obviously not their intention.

If you decide a new thread, I can split off posts from this thread to the new one. Just tell me which posts and where the new thread is. Back to this topic, no kidding on slow download. Might not get to it today. I have already prepared the testing system, it uses this board: http://www.ecs.com.tw/ECSWebSite/Product/Product_Detail.aspx?DetailID=1371&MenuID=17&LanID=0 It is UEFI that does not allow a 64bit boot, I just confirmed I can't PXE boot with it.

It is in the forum rules: Your other tool thread is hidden. Do not recreate it.

Its not surprising. Email providers already do a fair amount of scanning when an email hits the mail exchanger. For example, this can be were blacklists are used to filter out spam.

UEFI is a firmware just like BIOS is. PCs with UEFI firmware "can" emulate BIOS. I say "can" because it isn't a requirement. Manufacturers may include this option as a compatibility for legacy operating systems. This is typically termed as a CSM even if the "BIOS" menus don't have options to configure it or use that term directly. Some menus do not use the term CSM, but instead "Windows 8 mode" as (initially) Windows 8 certification required UEFI 2.3.1, which is why initial launch products came with 64bit Windows. As of now, there is no such thing (that I am aware of) as a UEFI 32bit PC. Remember the UEFI 2.3.1 spec was designed to eliminate 32bit, so they are natively 64bit. All UEFI "32bit" systems I have encountered are actually 64bit with a firmware limitation to support the boot of only 32bit MBR or GPT disks. You can think of these systems as being lacking of a proper CSM. So to clarify our use of (seemingly) outdated terms... BIOS is the "old" computer firmware, but it is also a term referring to booting an MBR disk. Another term for this is Legacy boot. And since the term BIOS is also (for many years) referred to the BIOS Setup menu we can enter at boot to configure said BIOS settings, it is difficult to just stop calling those menus BIOS. So we are not now (on modern hardware) entering the BIOS, but the UEFI. But we have called those menus BIOS for so many years... and with exception to the new Visual BIOSes on Intel, Asus and MSI boards, many manufacturers still sell products where the Setup menu looks the same as their older BIOS based systems. So understand the various ways people may use the term, then you can probably figure out which meaning they mean. I can't speak specifically for Linux, but I would imagine that in order for it to boot on any specific platform, it would require the appropriate boot rom. In my own experience with Recovery DVDs, I specifically deal with UEFI x64 systems, so the DVDs can boot in legacy or on UEFI systems in x64 mode. Being a "victim" of initial pre-launch Windows 8 requirements, we pretty much eliminated x86 OS support on the UEFI hardware, so no testing of multi-boot (BIOS vs UEFI mode) Recovery DVDs were done on the firmware locked x86 booting hardware. Of course, as myself, I don't delve too deeply into the structure of this or that (I leave that to jaclaz) and instead go for the "let's see if this works" approach. Thinking about this, if you have a concern about whether or not said ISO can boot on the x86 locked UEFI hardware, I MAY still have that board available to me to test with, providing you can give instructions on how to make the boot media.

That post you have found the x64 EFI boot file but not what architecture the WinPE is.

My county's Sheriff department was revealed (earlier this year) to have one of these devices. It wasn't said where it was, but it was actually found during an inventory/budget audit.

Speaking with some norms IRL (none of whome were named Norm, ironically) actually had that in their head. I was asked many times from friends and family members if they had to buy a new computer because their XP would stop working. I blame the FUD being spewed from the television news stations giving this impression.

Anyways, questions of my own regarding this WinPE5 image. What is its architecture? Windows 8 brought out an "apology" of sorts from Microsoft, who had intended to see x86 disappear completely (in collusion with Intel and the others who drafted UEFI 2.3.1) and obviously this hasn't happened. As a result, Windows 8 (and WinPE as evidenced by Server 2012 PXE boot roms) have the ability to do a UEFI boot on both x86 and amd64 platforms. Although, I do not know if they can be interchanged, as I solely deal with 64bit UEFI booting.

There was a hardware problem with the server. We also have a status/check-in place for when the forum is down: http://www.ryanvm.net/forum/viewtopic.php?t=10296

I feel the SP1 WAIK is a needless update. The only difference between it and RTM was the winpe image itself.

Welcome to the MSFN!

When my boot drive started to fail earlier this year, after I cloned it with ghost (disk-to-disk) and booted with the new disk the first time, it ran a checkdisk. But it didn't do it every time I turn on the PC. The filesystem may have been damaged from the old drive and hopefully that is all it will fix. There shouldn't be bad sectors on the new disk, if there is maybe you can get it replaced under warranty?

This user updated to Windows 8.1, as per their thread on Technet: http://social.technet.microsoft.com/Forums/windows/en-US/1ae70c1b-a761-4b92-8b71-531f234c2038/cannot-boot-from-windows-8-notebook-error-operating-system-version-is-incompatible-with-startup In my initial testing of using stock MS recovery, there was no problem recovering Windows 8 after it had been updated to Windows 8.1. I never tried Startup Repair in that testing.

Embedded has changed from 7 to 8. For the most part, installing the OS from the DVD isn't quite enough for Embedded 8 products, as certain things do not work properly. I would build a new image/configset using ICE, reinstall 8.1 Industry Pro with the new media, and see if it works any differently.

Using java.com as an example of course. This article highlights how malware is being delivered via advertisements which, in itself, is not a new or newsworthy concept. It is a different variant of "malvertisements" and should still be pointed out. http://blog.fox-it.com/2014/08/27/malvertising-not-all-java-from-java-com-is-legitimate/ I found the story via: https://twitter.com/dragosr/status/504647585227755520

I think the limitation that both UIs can't be had is going to be a mistake. Currently, you can have a Windows 8.1 with both UIs if you use StartIsBack or another menu replacement. The reason why I think it is going to be a mistake is that I'm just starting to see people be interested in the games available from the Windows Store. People that want a dual experience as in Windows 8.1 are not going to like Windows 9 if the same experience can't be had. Of course, the initial mistake was forcing the Modern UI onto desktop users.

See your post in the Windows 7 unattend section. Although you may find Vista and Win7 XML is mostly the same.

How the OOBE phase works is, if the installation does not have the information it needs, it will show you the appropriate page. So if you don't want those pages to appear, you need to have the correct information it needs in your XML. To choose an OS: <ImageInstall> <OSImage> <InstallFrom> <MetaData wcm:action="add"> <Key>/IMAGE/NAME</Key> <Value>Windows 7 PROFESSIONAL</Value> </MetaData> </InstallFrom> </OSImage> </ImageInstall>To choose a Time Zone: <TimeZone>Central Standard Time</TimeZone>To add an activation key: <settings pass="specialize"> <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <ProductKey>XXXXX-XXXXX-XXXXX-XXXXX-XXXXX</ProductKey> </component> </settings> While you can find example XMLs in many threads in this section, we have a highlight thread:http://www.msfn.org/board/topic/139572-ask-your-seven-xml-here/ Also, make sure to use the Unattend.chm to look up the different objects like ProductKey, etc. In my example above I made sure to show the activation key is used in the Specialize pass, but as you can see in the documentation, you can put a product key in other places for other things. The information in the CHM is also available on Technet, but I personally prefer to use the CHM. PS: I am removing your topic tags as they are not made properly.