The link to the Windows 7 DDK (or WDK) is not something I seem to be able to get to.
I need to write a driver that will convert the content to XPS and then do something with it. The "do something" is easy, but its the first part I'm not sure of.
I found links to the Win7 WDK but as I said above I can't get to it (my company has MSDN but I can't find it in the downloads).
As for the XPS part, I found this link which talks about XPS now available, and the resulting link to here doesn't seem to focus on drivers at all and seems more general.
I'm wondering if anyone can help with these two issues. Is writing a driver for Win7 much the same as Vista, in which case I can at least get started with the Windows 2008 WDK? And has anyone used this XPS filter pipeline to print to XPS with their own custom drivers?
Appreciate all help.
You can find a link to the Windows Driver Kit (WDK) 7.0.0 on the How to get the WDK page.
For driver development, XPSDrv drivers developed for Vista (and the downlevel redist for XP & Server 2003) are compatible with Windows 7. However, Windows 7 adds new Win32 APIs that can be used within an XPSDrv and help with manipulating XPS content and provide a driver-safe rasterization capability.
Related
Has anyone used WTL on Windows 10 already? All applications that I create with WTL segfault on Windows 10. They work on Windows 8 and Windows 7.
I even tried the most basic Hello-World application in WTL on Windows 10 and it segfaults when I run it. There are no clear indications of what is wrong. The program just segfaults with generic Windows segfault error.
Looks like WTL isn't Windows 10 compatible yet? Has anyone had this problem yet.
Just asking here as others will probably have the same problem. I tried two different Windows 10 (pre-release beta, and official release). I'm using latest WTL version WTL 9.0.4140 Final (2014-05-30).
All of our commercial applications are WTL built in VS2008. They work fine on Windows 10. If you can get a dmp file you should be able to review the crash dmp in windbg and see what is causing the fault.
Windows 10 with Visual Studio 2015 Community compiles and runs WTL sample MemDlg, I used WTL91_5270_Beta
our commercial video application is WTL-based(vs2015 express).
work fine, but it act different to MFC-based applications.
when win10 menu popup, video frame-rate drop in MFC(26fps->10fps), WTL(26fps->5fps).
https://github.com/sailfish009/wtl (WTL Version 9.1 (build 5321 final) 2015-11-17)
I am a little confused. When I search the internet I see examples of Windows CE running on Raspberry Pi or Samsung ARM11. However, I cannot be sure if they hacked it somehow or CE officially runs on ARM devices.
If it does not, should I use Windows Embedded products to target arm processors?
And the last question is that How does Windows CE fare when compared to Windows Embedded 7 in terms of footprint?
Can anybody enlighten me please?
Yes, Windows CE (lately renamed Windows Embedded Compact) runs on ARM. Up to version 6 it supported also SH4 and in Compact 7 MIPS.
Latest version is named (confusingly) Windows Embedded Compact 2013 and Microsoft is committed to support it up to 2023.
It's a different kernel (real-time) but provides some compatibility at the API level with desktop and server versions.
The new Windows IoT Core version runs on Raspberry Pi 2 (ARMv7) and uses the same kernel of the PC version.
Microsoft used an ARM build of Windows CE for Windows Phone 7, 7.5, 7.8, before they jumped to running NT on their ARM phones. For sure it exists.
I can't figure out if you can actually get it though. They have "Windows Embedded Compact 7", but from the documentation, it sounds like it's only x86 and amd64. But maybe there's some way to get the ARM version... maybe an MSDN license or by being some kind of business partner with Microsoft?
On second thought, this link: http://www.microsoft.com/windowsembedded/en-us/windows-embedded-compact-7.aspx suggests that it does work for ARM.
Bonus: Apparently Windows 10 will run on the Raspberry Pi 2: http://arstechnica.com/information-technology/2015/02/windows-on-arm-lives-on-even-as-it-dies/ The only question is if they'll keep requiring every non-app .exe to be signed by Microsoft like they did with the surface RT, preventing normal win32 or .NET programs from being possible to develop for ARM on NT. If they don't give us that crazy restriction, this could be pretty neat.
Microsoft no longer supports VB6 development and support from Microsoft has already stopped. But VB6 applications still run on Windows 8.1. See also this article titled "Support Statement for Visual Basic 6.0 on Windows Vista, Windows Server 2008, Windows 7, Windows 8 and Windows 8.1".
When would a VB6 application stop running on Windows? Is there any official statement from Microsoft or any clue about the same?
EDIT:
In this link, the Visual Studio team has mentioned that, "It will be supported at least through 2024". But it's not clear whether they said it's supported in Windows 8 till 2024 or in future release of windows OS too.
The "2024" means as part of Windows 8. The link says the VB6 runtime is part of Windows and therefore will be supported in the same way as the rest of Windows. For example Windows 8 will be supported until 2024 because that's the support lifecycle for Windows 8.
EDIT: Microsoft have now said the VB6 runtime is officially part of Windows 10 too.
EDIT: the VB6 IDE (not runtime) is no longer officially supported on any version of Windows, but there are ways to get it to work on Windows 7 and 8.
Uservoice: The VB6 runtime it is still a component of the Windows operating
system and is a component shipped in Windows 8.1. It will be supported
at least through 2024
It seems clear they mean VB6 will be supported through 2024, not just VB6 on Windows 8 (whose mainstream support ends 6 years earlier anyway).
The VB6 programming language installs and runs on Windows 7, 8.x and 10.
There is a utility to install it here: VB6 IDE install utility
It is in Microsoft's interests for VB6 applications to run in Windows 10 and so they probably will. The same is probably true of most old application frameworks: Microsoft works hard to maintain compatibility. The IDE runs on Windows 7 (not sure about 8 or 10).
However, just because Microsoft says VB6 will run it doesn't mean your particular application will work, particularly if you use third party components. You should at least be thinking about migrating to another development environment.
From what I heard, VB6 applications still work on Windows 10 technical preview. I've seen no official statement yet, but it would seem that VB6 will stay supported for at least a few years.
Microsoft have just stated for VB6 programming on Windows 10:-
"Windows is committed to compatibility. The Windows compatibility team
has been looking at user telemetry and reacting to feedback from
Windows Insiders to ensure that existing apps work well with Windows
10. Windows 10 is designed to run Windows 8.1 and Windows Phone 8.1 software programs. And yes, everyone’s favorite VB6 Runtime will
continue to work, too. In the near future, the compat team will go
more in-depth on this topic on Blogging Windows."
Everyone's favorite VB6 programming on Windows 10
So VB6 programming will work on Windows 10, as does VBA programming.
They also state that 'Project Centennial' Universal Windows Platform Bridge will work with VB6 code.
Instructions for installing the VB6 IDE are available here...
In my personal experience if you build a dll in VB6 and add it as a component to COM Plus in Server 2016 it just won't add. You will get an error such as the following, even for a 'Hello World' component.
A registry value was changed while installing the following component
into a COM+ Application. If you are experiencing activation problems
with this component then please check the registry value for the
following key.
Component: C:\temp\Project1.dll
Registry Key:
CLSID\{D5DE8D20-5BB8-11D1-A1E3-00A0C90F2731}\InProcServer32
Process Name: RunDll32.exe Comsvcs.dll file version: not loaded
There is a project to provide a new language "RADBasic" which is intended to be compatible with the VB6 programming language.
New language compatible with VB6 programming
Looks like Microsoft just extended VB6 runtime support out to Windows 11 and Server 2022. No such luck for the IDE though.
Read more from Microsoft here:
https://learn.microsoft.com/en-us/previous-versions/visualstudio/visual-basic-6/visual-basic-6-support-policy
I am going to write USB printer driver for Windows Embedded CE 6.0. But I dont know from where to start. Now I installed VS2005, patches of WinCE6.0, VS2005 team suite SP1, Platform Builder SP1, R2,R3.
Tell me how to start to write the driver, whether from VS 2005. In which application I am going to write the driver application. How to use platform Builder, how PB is helpful for me to write the USB driver.
I have Win CE 6.0 device is with me. Plz help me .
pcl.dll is not working for this device. plz tell me how to write driver, steps for it.
If you want to plug a printer into your CE device, start with the source found on your PC at:
C:\WINCE600\PUBLIC\COMMON\OAK\DRIVERS\USB\CLASS\PRINTER
If you want your CE device to act as a printer, start with the source found on your PC at:
C:\WINCE600\PUBLIC\COMMON\OAK\DRIVERS\USBFN\CLASS\UFNPRN
Clone the code to your BSP (do not modify the code in the locations above), make the modifications and then do the build/sysgen/makeimg as necessary. Iterate until you have what you want.
Good afternoon,
WinUSB is working well on the development computer that I am using (Win XP SP3). I am able to download new firmware to the Cypress FX2, and then connect to the new USB device once it 'renumerates'. However, if I've tried the same code with the WinUSB driver on a few other computers (Win XP SP3, Win7 x64) and they both returned the error "A device attached to the system is not functioning." when trying to use CreateFile to get a handle to the USB device.
The devicePath was found successfully, so I'm not sure why it cannot connect to the device. Furthermore, the device manager states that my device is working properly. I'm curious if I'm missing something when compiling the code? I would guess that my development computer has something installed on it that the other computers do not? Or perhaps it's a power setting and the device is going to sleep (although I've fooled around with the Power Options on each computer to no avail).
Does anyone have any ideas? I've compiled under Visual Studio 2008, and have installed the Microsoft C++ 2008 Redistributable Package on the computers that I've tested on.
Thanks,
Giawa
Solved: The GUID that my driver was using was shared with another device on the system, which was returned instead of my device. The device just happened to not be installed on my computer. I've generated a new GUID and everything seems to work now.
Giawa