Other > Computer News
Windows 10
DaveLembke:
Thanks BC for sharing this http://technet.microsoft.com/en-ca/sysinternals/cc817881.aspx
I didnt know they added this as an optional download addon for Windows from sysinternals. Very Cool... Im going to have to check this out on home pc. 8)
DaveLembke:
Testing with Windows 10 Beta 32-bit .... its actually not that bad and fast to get to desktop on older computer which was surprising.
Testing using a HP DX2300M ( Pentium D 2.8Ghz, 1GB RAM, Integrated GPU, 40GB SATA HDD)
Only trouble so far is with an old error that I remember seeing a while back with Windows XP and a update that broke running 16-bit applications on 32-bit OS.
Exact message in the box is:
--------------------------------------------------------------
16-Bit MS-DOS Subsystem
C:\Windows\System32\cmd.exe - edit test.txt
NTVDM has encountered a System Error
A device attached to the system is not functioning.
Choose 'Close' to terminate the application
[ Close ] [ Ignore ]
--------------------------------------------------------------
So EDIT doesnt want to work from command shell. I am going to try this out on another computer I have to see if there is a true problem here or if there is some strange issue between this older computer and the Windows 10 beta before posting this as a real problem to the MS Forum for Windows 10 beta.
Anyone download and test the beta of Windows 10 (32-bit x86 ) yet to confirm if they are also having the same problem I am having with edit from command shell?
In regards to the statement in the error message of: "A device attached to the system is not functioning."
My thought on this is to check the HDD first to make sure its healthy. I know this drive is healthy and ran a check disk on it and all is well. I also ran crystaldisk info on this same drive prior to this under a build of Windows 7 64-bit and everything was good health wise and only 18,000 hours on the drive and 1200 cycles of power to it and reallocated sector count remained at 0 which is good.
So this issue might be similar to the XP issue of years past and it popping up with 16-bit applications after a security update broke 16-bit applications run from command shell.
Also to add.... prior to running edit, I was just testing out random features of the command shell and when running MEM to display memory, the Windows 10 (32 bit x86 ) had to install NTVDM before MEM would function. After it installed the internal Windows component MEM then worked properly.
The next command was EDIT test.txt and thats when the error popped up. I then rebooted and tried again and MEM shows memory without any issues from command shell and running EDIT again popped up the same error message about the 16-bit application.
Lastly I was surprised that they removed the top right menu that was part of 8 and 8.1 from Windows 10. I actually dont mind it missing, but those who have come accustomed to Windows 8 and 8.1 may find themselves clicking the top right corner with nothing happening until they break the habit or microsoft adds this dual navigation for Start Menu -or- Top right Corner to not be awkward to 8 and 8.1 users going to 10.
BC_Programmer:
I have the x64 version installed in a VM. I'll install the x86 version and see if the same thing occurs.
What edit.com are you using? Is that included in the x86 version?
The top-right menu (charms) still there, at least Win+C shows it. the option is in the taskbar properties->Navigation tab, under "When I point to the upper-right corner, show the Charms". But it might be broken. Can't get it to do that in the VM.
FWIW Edit works in my XP SP3 VM. When the x86 install finishes I'll try it there as well.
BC_Programmer:
OK, it finished.
Start->Run CMD prompted me to install the feature (NTVDM)... I allowed it. After it installed, Edit launched just fine.
DaveLembke:
--- Quote ---Start->Run CMD prompted me to install the feature (NTVDM)... I allowed it. After it installed, Edit launched just fine.
--- End quote ---
Cool thanks for checking on this. I will try this on a different box and see if its some odd issue with Windows 10 and hardware of some kind. Also I will grab another HDD that I have and install Windows 10 to that drive on this same box to rule out any possibility of a drive problem, even though the drive was healthy when running prior OS on it.
As far as which edit I was using its the one that came with the build located at c:\windows\system32\
As far as the version of Windows 10 I only saw 2 ISO downloads available one for x86 (32bit) and the other for x64 (64-bit) that were English. I downloaded both of those and burned them to DVD-R.
Its interesting that NTVDM had to be installed to allow functionality of some of the command shell legacy features, when all prior Windows versions didnt require installation of any internal feature to allow legacy command shell functionality. Curious as to if this was intentional for security ( since why allow command shell features if your a home user that is strictly a GUI user and not a developer or an admin etc ) - or - because they are likely trying to steer away from the legacy command shell in the future and this is 1 step closer to its removal.
Thinking of Windows without a command shell, I would feel very restricted, and confined to only abilities that are part of Windows and applications or having to write programs that run only in GUI to do what i do so quickly within the command shell environment.
If it is for security reasons that they are eventually doing away with command shell, I dont see why they wouldnt just implement bare minimum privileges at the command shell, and require elevated privileges to do anything nasty from it. Similar to Linux distros requiring sudo. To do anything nasty credentials would have to be known for the targeted system(s).
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version