I'm deploying windows 10 via SCCM on new computer it loads into PXE then reboot.. When I try ipconfig I'm not getting ip so I though it will be problem with NIC.. so I tried to load all available drivers for this desktop and still not working.. I'm out of ideas..
Thanks
"so I tried to load all available drivers for this desktop and still not working.. "
Did you mean that you add all drivers of this model into the boot image which associated with the OSD task sequence? If so, that is not recommended by MS. You should only import the actually required NIC drivers or storage drivers into the boot images(both x86 and x64).
Another important point here is you should add the NIC drivers match the boot image version instead of the OS version you are trying to deploy. For example, add NIC drivers for win10 to the boot image 10.x.xxxxx (which is from the ADK 10 RTM or later).
Related
An application, consists basically on a communication between a microcontroller and a pc, is running perfectely on Windows 7 64 bits. Since i have windows 10 installed, the application doesn t work anymore. Even the serial communication isn t established. ( an error shown that the application can not establish the communication)
I have verified the microcontroller with other Terminal running on Windows and no Problem within. Also i think that the Problem could be on the Code, the application was created with visual Studio, well i don t have any experience with visual Studio,so that i would ask you if there is a way to check that this application for instance will not work on Windows 10!
Thank you in advance
You indicate that the application will run, therefore it is unlikely that the application is incompatible with Windows 10. You're getting an error saying that the application is unable to communicate with the serial port, so the application is opening. Most applications which flat out won't work with Win 10 use older, unsupported versions of .Net or expect a FAT filesystem and simply won't run.
This suggests that Windows 10 did not have a native driver for your serial port. This is not too shocking; the older pin serial ports currently see exclusive use and are replaced (for most users) by USB-connecting components. I would check the computer's Device Manager. If you don't see any serial ports there, or see them but with an error, Win 10 probably did not have the driver required. From there I would contact the motherboard or serial bus card manufacturer for updated drivers, if they exist.
I know that there is a simple driver example to install a device driver on IoT Core. I cannot find any information about how to install a NetService type NDIS filter driver on IoT Core. I have trouble installing a NDIS Filter Driver on IoT Core, which is quite different from a general device driver.
My NDIS filter driver is basically from VS2015 NDIS filter driver sample. I already successfully put it on a target Win 10 Enterprise PC and can see its trace messages via VS2015 Kernel debugger window from Development computer.
I was also trying to put it on Windows IoT Core, and my hardware is Minnowboard Max. My steps are:
Follow
https://ms-iot.github.io/content/en-US/win10/samples/DriverLab4.htm
to just set up the provisioning on the target IoT Core from VS2015
on dev computer.
Follow
https://channel9.msdn.com/Blogs/WinHEC/Creating-Universal-Drivers-with-WDK-10
to prepare for the mobile package (.cab file). Need to enter the
required info in Package.pkg.xml file. Build the x86 debug version.
Follow the same link as bullet 2 to deploy the .cab (online .cab package installation/update) on IoT
Core from VS2015.
However, after connected via Kernel Debugger and set Kd_DEFAULT_MASK
= 0xF, cannot see any filter driver’s trace messages.
“devcon listclass NetService” returns empty.
Can anyone give me any instructions or hint? (This issue
is only for IoT Core. I successfully made it work on Windows 10 Enterprise already.)
Unfortunately I don't think that NDIS LWFs can be installed onto Windows IoT Core currently. What's the high-level problem you're trying to solve? Maybe there's another way to solve this problem that doesn't involve LWFs.
Is it possible to deploy Windows 10 IoT (Rasp Pi image) as a Virtual Machine using VirtualBox or VMWare Player?
I need for a testing lab a network of three to five Windows 10 IoT devices. A virtual cluster would be perfect. My Google- and Bing-based research failed.
The problem could be either the non-ISO disk image file format or the non-x86 architecture of the operating system, couldn't it?
The easiest way I found is downloading Windows 10 IoT Core for MinnowBoard MAX
(here: http://go.microsoft.com/fwlink/?LinkId=691712). This MinnowBoard is x86-based and the image comes in a .iso file. I know the OP was specific about being a Rasp Pi image, but I don't really see the difference if we're just trying to use a hypervisor. Afterwards, you may just follow this tutorial: http://www.newventuresoftware.com/blog/running-windows-10-iot-core-in-a-virtual-machine
It's very simple and straight-forward, and it works with VirtualBox.
Based on #makoshichi's links here's the steps that worked for me:
Download MinnowBoard MAX IoT Core from microsoft, and install
Run ImgMount tool as Admin to mount "C:\Program Files (x86)\Microsoft IoT\FFU\MinnowBoardMax\flash.ffu"
Detach the VHD from Disk Management (in Computer Management), move the resultant .vhd file (that it informs you of on detach) to a location of your choice
Create, but don't launch, a new Virtual Machine in VirtualBox (expert mode) as Windows 32-bit, using an "existing virtual hard disk file" - the one you just moved
Goto device Settings->System and click Enable EFI (special OSes only)
Goto device Settings->Network and select Bridged Adapater
That's it - Run your virtual machine and be a happy Thing of the Internet, or something like that.
This is my short version of this wonderful post by Yavor Ivanov.
The QEMU emulator may do it, it will boot the image file directly. you may need to expand the ffu with dism first.
You don't have to fully install w10 preview: just boot the W10 real or virtual DVD and select to open a cmd box, from there you can run the updated dism command.iot w10 have no (direct) GUI, you must talk to the device via winrm and powershell
There is a good startup for you on
sourceforge
fc
https://github.com/0xabu/qemu/tree/raspi is a working way to run Windows 10 IoT on Qemu. It fully emulates a RPi2, except USB
Hi you could use the Raspberry Pi Simulator https://learn.microsoft.com/en-us/azure/iot-hub/iot-hub-raspberry-pi-web-simulator-get-started
I am working on a driver for a remote desktop server. Something like UltraVNC(in house protocol).
First of I see that mirror drivers are not supported on windows 8.
Only subset of DDI as a remote display driver.
1)
Does that mean I need to implement Remote Display Driver for windows 8?
2)Starting of with mirror driver and only adding the DDI specified here enough to have Remote Display Driver run on windows 8 (Will it install no windows 8)? It says that remote display driver is a subset of mirror driver.
http://msdn.microsoft.com/en-us/library/windows/hardware/hh974665(v=vs.85).aspx
3) Are there any any any examples? It looks like the mirror driver example is no where to be found ?
UPDATE : (on wdk 7.1) I found these examples.
4) I looked at Utlra VNC server source and It looks like they only have drivers up to Windows 7. However VNC SERVER still supports windows 8(for that it just does GDI stuff on user level to get the image update). So they have not implemented it.
There is a Remote Desktop Protocol Driver. Can that be used ?
5) what is the best place to start ?
Is this windows' way to limit remote desktop server implementation so that it is harder to compete with RDP.
6)
if implementing windows 8 implementing the DDIs necessary to have remote desktop driver is not enough to run it on windows.
Is the api below only way to do it on windows 8.
http://msdn.microsoft.com/en-us/library/windows/desktop/hh404487(v=vs.85).aspx
On Windows 8, there is a "Desktop Duplication API". With this API, it seems that you do not need to develop a driver anymore. Doc is here.
The "Remote Display Drivers" documented here is a bit mysterious...
I would like to create my Kinect development environment and am contemplating using iMac as the box with Windows 7 installed as dual boot and/or parallels.
Has anyone tried this configuration earlier and does it work?
Running Bootcamp(dual boot) works with windows 7/8 Parallels does not.
I have a macpro 1,1 and a mac air both work with bootcamp(dual boot).
The only thing that could cause it not to work is the USB configuration. Kinect requires that it be connected to a USB host controller and not a hub. I believe all of the iMac's USB ports are host ports so I don't believe this to be an issue. If you use the Kinect Sensor Chooser control built into the WPFViewers sample app it will tell you if that particular problem arises (insufficient bandwidth).
Parallels will not work with the SDK at the time of this writing due to driver. Kinect is not an official USB device and the driver requires direct communication with the Kinect. I hoped that this would be resolved with the official Kinect for Windows hardware but alas it was not.
You might want to look at native OSX Kinect development using OpenKinect
http://openkinect.org/wiki/Getting_Started
If you don't want to have to write all the image processing code yourself, and are working in C#, you could start with the Accord library:
http://accord-net.origo.ethz.ch/