Tripredacus

It may be possible to locate your old account by using the email you used to use. Also you will need to remove the link in your signature as we do not permit advertising. If, after you are contributing to the community, you want to show off your website, you can post about it here: http://www.msfn.org/board/forum/4-websites-and-boards/

Having worked for an ISP before, I can tell you that anyone at Google who has the ability to log into the mail server or mail exchangers, can read any email they want.

That EULA is for POSReady 2009, however WES 2009 has the same limitations in its EULA.

That's a normal behaviour. I use the text mode always unless I want to add a smiley. I too notice that the hard returns get nerfed when switching between modes. Also another thing I notice in your new screenshot... The quick-reply box is there as it is showing your name as "photo" but it is not rendering. But the accounting doesn't seem to see you as being present. Even if you were logged in as anon, it would show you as JorgeA and 1 anon or 1 member. But your pic shows only 2 guests. Make sure you are not blocking this URL: ajax.googleapis.com It is required in order for the reply box to work properly. For example, if I block that URL, the quick reply ceases to function.

I use it. There are some functional differences between an Embedded OS and a desktop one, but your question of "will it work with my programs" cannot be answered by us. That is why I said for you to try it out yourself to see if it suits your needs. We can't guess what your programs are and how they operate. I do know that some programs do not operate as expected based on feedback received from ISVs.

2 things. First, in your FF28 mode where you can't type (I'm using FF28 as well) it looks like you can still click the first button on the toolbar. This changes the editor mode to text only instead of wysiwyg mode. Try hitting that and see if you can type. Second, in both of your screenshots, the URL seems wrong. If you were replying to a topic, the URL wouldn't be board/index, but it would show topic/number-topic-title. For example, replying to this topic I have the following in my address bar: One last thing, does the quick reply box also not work?

Oh yeah, I forgot about Blaster, that was for a month or two. No way could you put a naked PC online, it would get infected right away. It was definately a pain during deployment, so many machines would get infected in that short period of time between when the NIC got an IP and the firewall software got installed.

Have you ever had to take a tech support call from someone with absolutely no grasp on how computers work or the terminology? Have you ever heard those stories of a rep telling a caller to close a window and they go and close an actual window in their house? The following image reminds me of talking to those types of people and how their strange world might work.

I have certainly seen PCs just become infected off the bat if connected to the internet with no AV or firewall. It is always due to special circumstances, such as in the early stages of a virus outbreak. The last time I've specifically seem this occur was during the first week of Conficker/Downadup before any patches were released.

Welcome to the MSFN!

I think it is more that MS had brought that message to the wrong audience. People at E3 are looking for consoles and video games, not those other features the XBox One and the PS4 have. A similar *yawn* occurred during Sony's conference this year (which was boring anyways) when they brought up their Playstation TV product. They should have been selling those products (or those features) at more relevant conferences like CES.

A good example, a 5 year old, visiting my house over the weekend for a get together, apparently had never seen a CRT computer monitor before. :\

Welcome to the MSFN!

More: http://walyou.com/worldwide-places-hit-by-the-blue-screen-of-death/

I would test out the applications on the Eval version first: http://www.microsoft.com/en-us/download/details.aspx?id=14947

I primarily run all my wmic commands in a .cmd. You can try this, I didn't test it out, just edited for syntax highlighting. RunWait (@ComSpec & " /c wmic useraccount where " & Chr(34) & "name='username'" & Chr(34) & " set passwordchangeable=false")

Use wmic wmic useraccount where "name='username'" set passwordchangeable=false

I would have mentioned that, since I did see that WDFcoinstaller does exist in the driver package. However, installing KMDF package is NOT required in a Windows 7 OS for the MEI driver to work. The only time I've had to add that support package (or UDMF) is if I inject a driver that has a WDFcoinstaller and the result is that the OS bugchecks at boot. It is possible it would only do this for boot-critical drivers, which may be why MEI doesn't cause a bugcheck. (I do not know if MEI driver is boot-critical. Just a guess.) Since the OP had not mentioned bugcheck issues after adding the driver, I didn't mention it.

I think the only reason you would skip user creation would be if you are enabling the Administrator account. Otherwise, if you don't enable the Administrator account, you won't be able to log into the OS. I do not know what kind of disk space you would be saving by removing the UAC components. Are you dealing with a small hard disk?

Ah, there is no "old" driver for the 9 series MEI, or at least one that doesn't support Windows 8. I suspect that your older PE is missing a dependent file. You can try booting into your PE, and run Depends on the 3 .sys files the driver injects to see if you are missing something. You could also compare those findings to what the results are from the WinPE4 since Depends will give false positives. These files are called out in the INF: [SourceDisksFiles.x86]TeeDriver.sys=1,.\x86HECI.sys=1,.\x86wdfcoinstaller01011.dll=1,.\x863f3ca95b-3978-4168-b47b-5444f42d6c89.devicemetadata-ms= 1,, ;A metadata package file for EN - Win846a6fdbe-c823-4579-bab6-35f67e01f793.devicemetadata-ms= 1,, ;A metadata package file for EN - Win7[SourceDisksFiles.amd64]TeeDriverx64.sys=1,.\x64HECIx64.sys=1,.\x64wdfcoinstaller01011.dll=1,.\x643f3ca95b-3978-4168-b47b-5444f42d6c89.devicemetadata-ms= 1,, ;A metadata package file for EN - Win846a6fdbe-c823-4579-bab6-35f67e01f793.devicemetadata-ms= 1,, ;A metadata package file for EN - Win7 Another way to troubleshoot that would allow for easier work would be to re-create your WinPE3 using Make_PE so you have a better Windows interface. Intel has a newer MEI driver than what you are using: https://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=23746〈=eng&OSVersion=Windows%207%20%2864-bit%29*&DownloadType=Drivers

Also, look into trying to use an older driver to use in the older WinPE. You should try finding them on Intel's site. If you can't find an older one, post the HwID of the PCI device.

Not use CSS?

Also test multiple connections with IE. HTTP URL, HTTPS URL, IP, local path and even an FTP address.

Well, I get the same message on Microsoft sites. So we can give those guys some slack.

Welcome to the MSFN!