Where's the application crash dump on an XP SP3 machine? - windows-xp

It used to be that an application crash (unhandled exception) would create a mini dump in the %TEMP% folder on an XP machine, but it looks like Microsoft has changed this logic - maybe with an update.
When a user level application or a service crashes, does it still create a mini-dump? Where does it get saved?
PS: I'm not interested in the BSOD, system, or kernel dump. This pertains to a user level application crash that does not bring down Windows.

I installed the Debugging Tools For Windows and used adplus in -crash mode in order to get the dumps I wanted.

Are you asking about http://msdn.microsoft.com/en-us/windows/hardware/gg487440 ?
Ok, then I think you want to enable Dr Watson
http://www.scribd.com/doc/47267084/Capturing-Application-Crash-Dumps
http://serato.com/howtos/scratchlive/1925/how-to-enable-dr-watson

Related

Visual Studio Code on Windows server 2008

Can I install Visual Studio Code on Windows server 2008 ?
I am a developer but I sent the information to my administrators and they told me that the setup file crashes after launched
I get seput file from hee https://code.visualstudio.com/download
procesor: Intel(R) Xeon(R) Gold 6142 CPU # 2.60Ghz - 2.59 GHz
RAM: 8 GB
64-bit
virtual machine
1 CPU - 2 cores
Windows Server 2008
First time answering here so bare with my vintage reply formatting. (also pardon that i couldn't capture screen due to server is on a intranet that not accessible on this device causing a long reply)
Being a unfortunate fellow that need to work on legacy Systems and Application frequently, i happen to have a fresh 2008R2 server recently setup by my team's Server Admin with following specs:
processor: Intel(R) Xeon(R) Gold 5220 CPU # 2.20Ghz - 2.19 GHz ,
OS: Windows Server 2008R2 x64 ,
RAM: 8GB
The versions that is able to install was 1.70.3,which is the same version that is the last supporting versions for Windows 7 as well,if you happen to need to work on devices using that OS version.
although i'm uncertain whether it is a VM or not, i'd like to point out a few more things that your question did not cover but need to consider:
The installer version (System setup vs User Setup)
aside from the x64 |x86 | ARM installer differences, as you've not mentioned which versions of the build and which exact setup installer you sent to your admin, i've first replied which build version successfully installed on 2008R2, which as of writing the latest build was 1.73.0 and on run,it pop up a error message as follow regardless of System/User Setup:
This Program does not support the version of windows your computer is running.
in our current case that we want specific previous versions installer, VScode FAQ on previous versions have a URL lists that enables you to download a specific build version of your preferred setup. For my case (and also refer below to exactly why this one), i've go for System setup, and i know the aprox. supporting version was ~1.70.0, so i used the link as below and replace the {version} to start:
https://update.code.visualstudio.com/{version}/win32-x64/stable
Active Domain, Multiple user sessions etc.
Per VSCode requirements page stated,
VS Code does not support multiple simultaneous users using the software on the same machine, including shared virtual desktop
infrastructure machines or a pooled Windows/Linux Virtual Desktop host
pool.
as im not sure do you work solo or do have fellow colleagues to code on the server at the same time, you might need to reconsider to install using user or System setup.
if your intentions are to use exclusively on a specific AD account, then user setup should probably be good enough.
however, if the intentions was to setup say a shared Remote desktop connections on the VM that allows multiple RDC sessions simultaneously for coding,programming etc., so you intend to install a system setup to allow all users on said server to be able to use VScode, then you might run into the problem the VScode requirements stated it does not support.
in addition, as i was remote connected as administrator , when using a 1.70.2 user setup ,a different warning message as follow was thrown:
This user Installer is not meant to be run as Administrator. If you would like to install VS Code for all users in this system, download the system Installer instead.Are you sure you want to continue?
as the installer itself also checks with the operator on this matter, your admin may have skipped on the exact reasons why the install failed and just told you the installer crashed.
if you absolutely need VScode to run on the server but can't install for reasons, the last resort (aside from going for alternatives like notepad++) is to Setup a Portable Mode builds on your own workstation/devices first, then upload the package to the server and use it from there.
i wouldn't go into too much detail in that as this reply already span for a starwars trilogy length but keep in mind, version limitations still apply, and whatever add-ons you need, you need to download them first before bundle it into the package to upload and run on your server.
Anyone that is a System admin or infrastructure architects , do correct me on my novice understanding on Server settings etc. as although i'm primarily a programmer, i did end up touching a lot more things that i'm not specialized into over the few years of vendor career work so there bound to be incorrect/inaccurate concepts i spilled. cheers.

Run application as 32 bit in VS Code

I am trying to develop a small application which must interact with a very old version of access and pull the data out. We have a solution already in powershell but we want to move away from powershell and get it in C#
I think I have code that should work theoretically, but there's one setback, it must be run in 32-bit mode due to the age of the access version I'm working with. When I run my app, there are no exceptions, I simply get a message in my debug console that says:
The Microsoft.Jet.OLEDB.4.0' provider is not registered on the local machine.
The powershell has a requirement that it must be run in 32-bit powershell and after researching the above message I believe my application must also be run in 32-bit mode. I have also settled on using OLEDB to access the file, just as the powershell does, further adding to my assumption
I primarily use VSCode to develop here, but I am not above installing regular Visual Studio if necessary
I installed the 32-bit VSCode and ran my application there but I got the same message
How can I fix this?

Oracle SQL Developer 4.1.3 not loading in Windows 10

I've recently downloaded Oracle SQL Developer 4.1.3 from Oracle Website
and this with JDK as well, but I tried to run in windows 10, it only goes 10% of progress bar, then disappeared. Can't run it at all?
SQL Developer 4.1.3 can connect to Oracle 11g db, right?
I've found 2 things most likely cause what you're experiencing:
video driver conflict with windows and Java - this is usually what happens to cause the program to just 'disappear.' If you open a CMD window, CD to your sqldeveloper\bin directory, and run the exe from there, you should see some sort of Java 'crash' stack when the GUI goes away suddenly. And in there, you'll see a reference to a windows dll that belongs to the video driver. if that's the case, update that driver, and you should be good
the application settings for your OS user are corrupted. To fix, find your AppData, Roaming Profiles folder for 'SQL Developer' - there should be a system4.1.3... folder in there - rename it, and restart sql developer.

Run a program on Mac OS host from Windows running as parallels guest

On a MacBook Pro running Windows 7 in Parallels 7, I need to run a Unix Executable File on the Mac side via a command line invocation on the Windows side. In Windows Explorer, I can use Open on Mac, but I need a way to do this via a batch file or anything else that can be expressed on a command line. I was hoping that Parallels Tools might have a command that can do this, but I can't find anything.
This seems like it should be pretty straightforward, but my searches have turned up nothing.
I also tried creating an alias on the Mac side, which I added to my Applications folder. I was hoping that it would appear in Start > All Programs > Parallels Shared Applications, which might allow me to access it with a batch file. However, I don't see it. I'm not sure what it takes to add new entries to Parallels Shared Applications. Maybe a reboot would do it, but I have not tried that yet.
Thanks for any advice.
It seems like the Platypus app might be able to help with this. It wraps a shell script into a Mac App. Unfortunately I can't get Parallels to provide access to the Platypus generated app the same way it provides access to the other Mac apps.

Install device driver silently on Windows XP

Is there a way to programmatically install device driver silently without cat file and without connecting the device on Windows Xp?
I'm using DriverPackageInstall function from Windows Driver Kit. And I can install driver only if device is attached. In other case I get an error: ERROR_NO_SUCH_DEVINST. But that method works fine with Windows Vista.
Another problem is warning dialog that asks user to continue or stop installation because cat file is missing . It shows on both OSes.
Any ideas?
You're not going to get past the signing prompt, as this is baked pretty far into windows, but there is a tool in the DDK called devinst that works well for device installations.
There's Source Code included with it.
The only way to avoid any UI interaction caused by your driver being unsigned is to hackishly preinstall the driver by modifying the registry directly.
Yes, it can be done. You'd have to modify the ACLs on the HKLM\System\CurrentControlSet\Enum registry key run as SYSTEM (by installing yourself as a service or using Sysinternals psexec -s), and add all the registry keys which Windows device installation would usually add - on your own. This will only work if you can predict precisely what your device's Device Instance ID would be -- e.g. in case of a USB device, the precise port it'd be connected to etc.
This is hacky, but the result would be the device being essentially "preinstalled". It'll be a lot of work, and it'll break on Windows Vista.
Microsoft really wants you to go the WHQL way on Windows XP, sorry :(