How to debug applet on Microsoft JVM

Hi,
Right now I have a Java applet application written by Visual J++ and running on Microsoft's JVM. OS is WinXP SP2 with IE 6.
I want to write an external application to get the data from applet when Text Field's value is changed and also want to simulate to click button, input text, and press keyboard to applets.
I can make it if the Java applet application is running on Sun's JVM. It is because Sun provides JVMDI (Java Virtual Machine Debug Interface) and JNI (Java Native Interface) to monitor and control applets in browser. We can configure Java Plug-in to inject a DLL into IE browser to get the Sun's JVM runtime environment and then use JNI to operate Java objects. I have written several external applications for Sun's JVM using JRE 1.4.2_xx. And they work well.
But for Microsoft JVM I don't know if I can do the same thing. I wonder if Microsoft has the same interfaces or has another mechanism to handle this.
Any helps will be highly appreciated. Thanks.

the applet is in jar form right? that jar is just another bit of static content your site delivers, much like an image. put it in a folder inside your server-side application, where you put other static content, and link to it with a URL
for the future, you're better off not telling people how urgent your problem is - it's only urgent to you, and doing that can put people off answering at all

Similar Messages

How to debug applets

I'm a new at this.
Can anyone suggest of a way to debug applets. I'd love
to trace through statements in the code. How can I do it?
Thanks in advance.

Look into documentation provided by your IDE, it should provide example on how to dynamically debug an applet. Typically you would provide the html file (that loads the applet) name as a configuration parameter
HTH

Profiling tool for applets using Microsoft JVM?

Hello All,
I have an applet designed to work in Microsoft JVM. It is slow and sometimes crashes the browser and I doubted that it caused memory leak. Therefore, I wish to have a profiling tool which can collect time and memory consumption from Microsoft JVM.
Please advice.

simply: there is none.
Its even impossible to denug it withought a legal copy of J++, trust me MSJVM really sucks.
I have to create a really big applet which is compatible to Netscape-4.7 and MSJVM-3167+ and its nightmare. One change and the whole cardhouse breaks.
I do not want to make you feel sad, but leave it.
lg Clemens
PS: I would try to create as few objects a s possible, the ms-gc is not very powerful nore stable...

How does Java JRE impact Microsoft JVM

Supposing I download the latest Java JRE onto a PC, will it impact the programs that are currently using the Microsoft JVM ?

Check regedit with the oldvalueThanks -- I tried that. The old value is not in the registry, and all of the registry settings for java.home point to the correct directory. The java.home value that ends up inside the plugin must be determined some other way (at least in 1.4.2).
If anyone out there knows where it comes from, please let me know!
Thanks.

How to debug ABAP Web services from Microsoft Visual Studio

When developing .NET based Web services clients using Visual Studio that call Web services in SAP NetWeaver .NET developers would like to be able to debug inside SAP. In my blog <a href="/people/andre.fischer/blog/2007/02/07/how-to-debug-abap-web-services-from-microsoft-visual-studio to debug ABAP Web services from Microsoft Visual Studio</a> I would like to point .NET developers to the fact that SAP NetWeaver offers the option of external debugging to perform this task. Though the steps that have to be performed are described in the SAP Online Help I am sure that this option is not well known amongst the .NET developer community.

Hello WilliamIV,
>>How can I "configure" Visual Studio debugger to allow validation to work?
Since I do not have a VS2012 environment, according to your provided link, I created a test demo with VS2013, however, both ways catch the validation error:
If possible, you could have a try with VS2013 to see if it works or run the example on other machine with VS2012 to see if this is caused by the VS environment, in my side, I do not change any configuration, all are default.
If I misunderstood this issue, please feel free to let me know.
Regards.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

How to debug when you can't recreate error consistently

I have a simple illustrator-type application in which I draw rounded rectangles to a JPanel and then the user is able to move them around (the position and repaint is done in via the mouseDragged interface.
Sometimes, the application shuts down when I am dragging a box with this message:
# An unexpected error has been detected by HotSpot Virtual Machine:
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x6d236a0c, pid=3400, tid=2716
# Java VM: Java HotSpot(TM) Client VM (1.5.0_07-b03 mixed mode, sharing)
# Problematic frame:
# C [dcpr.dll+0x6a0c]
# An error report file with more information is saved as hs_err_pid3400.log
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
I checked the error report and it suggests the problem is within the PathFiller.WriteAlpha. The entire report is below. The problem I have is that if I restart the application and place boxes in the exact same locations as before, and try moving the one that caused the error, the error is not thrown.
I have no idea how to debug this as I can't even consistently reproduce. I just upgraded to the newest JDK (I think it was 7).
Thanks for any insight and help you can offer.
# An unexpected error has been detected by HotSpot Virtual Machine:
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x6d236a0c, pid=3400, tid=2716
# Java VM: Java HotSpot(TM) Client VM (1.5.0_07-b03 mixed mode, sharing)
# Problematic frame:
# C [dcpr.dll+0x6a0c]
--------------- T H R E A D ---------------
Current thread (0x00acae38): JavaThread "AWT-EventQueue-0" [_thread_in_native, id=2716]
siginfo: ExceptionCode=0xc0000005, reading address 0x00000007
Registers:
EAX=0x00a9c6b8, EBX=0x02e33930, ECX=0x00a9c6a4, EDX=0x00000001
ESP=0x0303f314, EBP=0x0303f328, ESI=0x00a35f1c, EDI=0xffffffff
EIP=0x6d236a0c, EFLAGS=0x00010286
Top of Stack: (sp=0x0303f314)
0x0303f314: 02e2865c 00a35f1c 02e33930 ffffffff
0x0303f324: 02e2865c 0303f34c 6d236ce8 02e33930
0x0303f334: 00a35f1c 02e33930 02e2865c 02e33930
0x0303f344: 00acaef8 02e34774 0303f378 6d2326be
0x0303f354: 02e33930 00a35f1c 02f13380 00000001
0x0303f364: 00000020 00000000 22fb02e8 22fad0d0
0x0303f374: 00acae38 0303f3a0 00b6a767 02f13380
0x0303f384: 0303f3b8 0303f3b4 00000001 00000020
Instructions: (pc=0x6d236a0c)
0x6d2369fc: 85 ff 89 7d f8 0f 84 16 01 00 00 eb 03 8b 7d f8
0x6d236a0c: d9 47 08 d8 15 50 c0 23 6d 8b 47 04 d9 55 fc 89
Stack: [0x03000000,0x03040000), sp=0x0303f314, free space=252k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C [dcpr.dll+0x6a0c]
C [dcpr.dll+0x6ce8]
C [dcpr.dll+0x26be]
J sun.dc.pr.PathFiller.writeAlpha8([BIII)V
J sun.java2d.pipe.DuctusRenderer.getAlpha(Lsun/dc/pr/Rasterizer;[BIII)V
J sun.java2d.pipe.DuctusShapeRenderer.renderPath(Lsun/java2d/SunGraphics2D;Ljava/awt/Shape;Ljava/awt/BasicStroke;)V
J sun.java2d.pipe.DuctusShapeRenderer.fill(Lsun/java2d/SunGraphics2D;Ljava/awt/Shape;)V
J sun.java2d.pipe.PixelToShapeConverter.fillRoundRect(Lsun/java2d/SunGraphics2D;IIIIII)V
J sun.java2d.SunGraphics2D.fillRoundRect(IIIIII)V
J writingplatform.PlatformNode.paintComponent(Ljava/awt/Graphics;)V
J writingplatform.TextNode.paintComponent(Ljava/awt/Graphics;)V
J writingplatform.PlatformPanel.paintComponent(Ljava/awt/Graphics;)V
J javax.swing.JComponent.paint(Ljava/awt/Graphics;)V
J javax.swing.JComponent.paintWithOffscreenBuffer(Ljavax/swing/JComponent;Ljava/awt/Graphics;IIIILjava/awt/Image;)V
J javax.swing.JComponent.paintDoubleBuffered(Ljavax/swing/JComponent;Ljava/awt/Component;Ljava/awt/Graphics;IIII)Z
J javax.swing.JComponent._paintImmediately(IIII)V
J javax.swing.JComponent.paintImmediately(IIII)V
J javax.swing.RepaintManager.paintDirtyRegions()V
J javax.swing.SystemEventQueueUtilities$ComponentWorkRequest.run()V
J java.awt.event.InvocationEvent.dispatch()V
J java.awt.EventQueue.dispatchEvent(Ljava/awt/AWTEvent;)V
J java.awt.EventDispatchThread.pumpOneEventForHierarchy(ILjava/awt/Component;)Z
v ~RuntimeStub::alignment_frame_return Runtime1 stub
j java.awt.EventDispatchThread.pumpEventsForHierarchy(ILjava/awt/Conditional;Ljava/awt/Component;)V+26
j java.awt.EventDispatchThread.pumpEvents(ILjava/awt/Conditional;)V+4
j java.awt.EventDispatchThread.pumpEvents(Ljava/awt/Conditional;)V+3
j java.awt.EventDispatchThread.run()V+9
v ~StubRoutines::call_stub
V [jvm.dll+0x86401]
V [jvm.dll+0xdb172]
V [jvm.dll+0x862d2]
V [jvm.dll+0x8602f]
V [jvm.dll+0xa0bcb]
V [jvm.dll+0x10bdad]
V [jvm.dll+0x10bd7b]
C [MSVCRT.dll+0x2a3b0]
C [kernel32.dll+0xb50b]
Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
J sun.dc.pr.PathFiller.writeAlpha8([BIII)V
J sun.java2d.pipe.DuctusRenderer.getAlpha(Lsun/dc/pr/Rasterizer;[BIII)V
J sun.java2d.pipe.DuctusShapeRenderer.renderPath(Lsun/java2d/SunGraphics2D;Ljava/awt/Shape;Ljava/awt/BasicStroke;)V
J sun.java2d.pipe.DuctusShapeRenderer.fill(Lsun/java2d/SunGraphics2D;Ljava/awt/Shape;)V
J sun.java2d.pipe.PixelToShapeConverter.fillRoundRect(Lsun/java2d/SunGraphics2D;IIIIII)V
J sun.java2d.SunGraphics2D.fillRoundRect(IIIIII)V
J writingplatform.PlatformNode.paintComponent(Ljava/awt/Graphics;)V
J writingplatform.TextNode.paintComponent(Ljava/awt/Graphics;)V
J writingplatform.PlatformPanel.paintComponent(Ljava/awt/Graphics;)V
J javax.swing.JComponent.paint(Ljava/awt/Graphics;)V
J javax.swing.JComponent.paintWithOffscreenBuffer(Ljavax/swing/JComponent;Ljava/awt/Graphics;IIIILjava/awt/Image;)V
J javax.swing.JComponent.paintDoubleBuffered(Ljavax/swing/JComponent;Ljava/awt/Component;Ljava/awt/Graphics;IIII)Z
J javax.swing.JComponent._paintImmediately(IIII)V
J javax.swing.JComponent.paintImmediately(IIII)V
J javax.swing.RepaintManager.paintDirtyRegions()V
J javax.swing.SystemEventQueueUtilities$ComponentWorkRequest.run()V
J java.awt.event.InvocationEvent.dispatch()V
J java.awt.EventQueue.dispatchEvent(Ljava/awt/AWTEvent;)V
J java.awt.EventDispatchThread.pumpOneEventForHierarchy(ILjava/awt/Component;)Z
v ~RuntimeStub::alignment_frame_return Runtime1 stub
j java.awt.EventDispatchThread.pumpEventsForHierarchy(ILjava/awt/Conditional;Ljava/awt/Component;)V+26
j java.awt.EventDispatchThread.pumpEvents(ILjava/awt/Conditional;)V+4
j java.awt.EventDispatchThread.pumpEvents(Ljava/awt/Conditional;)V+3
j java.awt.EventDispatchThread.run()V+9
v ~StubRoutines::call_stub
--------------- P R O C E S S ---------------
Java Threads: ( => current thread )
0x000360c0 JavaThread "DestroyJavaVM" [_thread_blocked, id=696]
=>0x00acae38 JavaThread "AWT-EventQueue-0" [_thread_in_native, id=2716]
0x00ac5530 JavaThread "AWT-Windows" daemon [_thread_in_native, id=3396]
0x00ac50b0 JavaThread "AWT-Shutdown" [_thread_blocked, id=2656]
0x00ac3eb8 JavaThread "Java2D Disposer" daemon [_thread_blocked, id=1644]
0x00a6ef28 JavaThread "Low Memory Detector" daemon [_thread_blocked, id=408]
0x00a6dc28 JavaThread "CompilerThread0" daemon [_thread_blocked, id=992]
0x0003fda0 JavaThread "Signal Dispatcher" daemon [_thread_blocked, id=1756]
0x00a42240 JavaThread "Finalizer" daemon [_thread_blocked, id=2156]
0x00a40d58 JavaThread "Reference Handler" daemon [_thread_blocked, id=328]
Other Threads:
0x00a3e460 VMThread [id=3024]
0x00a702a8 WatcherThread [id=1740]
VM state:not at safepoint (normal execution)
VM Mutex/Monitor currently owned by a thread: None
Heap
def new generation total 576K, used 20K [0x22a70000, 0x22b10000, 0x22f50000)
eden space 512K, 2% used [0x22a70000, 0x22a73220, 0x22af0000)
from space 64K, 12% used [0x22af0000, 0x22af2128, 0x22b00000)
to space 64K, 0% used [0x22b00000, 0x22b00000, 0x22b10000)
tenured generation total 1408K, used 435K [0x22f50000, 0x230b0000, 0x26a70000)
the space 1408K, 30% used [0x22f50000, 0x22fbcd10, 0x22fbce00, 0x230b0000)
compacting perm gen total 8192K, used 388K [0x26a70000, 0x27270000, 0x2aa70000)
the space 8192K, 4% used [0x26a70000, 0x26ad1170, 0x26ad1200, 0x27270000)
ro space 8192K, 67% used [0x2aa70000, 0x2afcd9f8, 0x2afcda00, 0x2b270000)
rw space 12288K, 46% used [0x2b270000, 0x2b813808, 0x2b813a00, 0x2be70000)
Dynamic libraries:
0x00400000 - 0x0040d000      C:\Program Files\Java\jdk1.5.0_07\jre\bin\java.exe
0x7c900000 - 0x7c9b0000      C:\WINDOWS\system32\ntdll.dll
0x7c800000 - 0x7c8f4000      C:\WINDOWS\system32\kernel32.dll
0x77dd0000 - 0x77e6b000      C:\WINDOWS\system32\ADVAPI32.dll
0x77e70000 - 0x77f01000      C:\WINDOWS\system32\RPCRT4.dll
0x77c10000 - 0x77c68000      C:\WINDOWS\system32\MSVCRT.dll
0x6d730000 - 0x6d8c7000      C:\Program Files\Java\jdk1.5.0_07\jre\bin\client\jvm.dll
0x77d40000 - 0x77dd0000      C:\WINDOWS\system32\USER32.dll
0x77f10000 - 0x77f57000      C:\WINDOWS\system32\GDI32.dll
0x76b40000 - 0x76b6d000      C:\WINDOWS\system32\WINMM.dll
0x6d2f0000 - 0x6d2f8000      C:\Program Files\Java\jdk1.5.0_07\jre\bin\hpi.dll
0x76bf0000 - 0x76bfb000      C:\WINDOWS\system32\PSAPI.DLL
0x6d700000 - 0x6d70c000      C:\Program Files\Java\jdk1.5.0_07\jre\bin\verify.dll
0x6d370000 - 0x6d38d000      C:\Program Files\Java\jdk1.5.0_07\jre\bin\java.dll
0x6d720000 - 0x6d72f000      C:\Program Files\Java\jdk1.5.0_07\jre\bin\zip.dll
0x6d070000 - 0x6d1d7000      C:\Program Files\Java\jdk1.5.0_07\jre\bin\awt.dll
0x73000000 - 0x73026000      C:\WINDOWS\system32\WINSPOOL.DRV
0x76390000 - 0x763ad000      C:\WINDOWS\system32\IMM32.dll
0x774e0000 - 0x7761d000      C:\WINDOWS\system32\ole32.dll
0x5ad70000 - 0x5ada8000      C:\WINDOWS\system32\uxtheme.dll
0x73760000 - 0x737a9000      C:\WINDOWS\system32\ddraw.dll
0x73bc0000 - 0x73bc6000      C:\WINDOWS\system32\DCIMAN32.dll
0x73940000 - 0x73a10000      C:\WINDOWS\system32\D3DIM700.DLL
0x6d2b0000 - 0x6d2ef000      C:\Program Files\Java\jdk1.5.0_07\jre\bin\fontmanager.dll
0x74720000 - 0x7476b000      C:\WINDOWS\system32\MSCTF.dll
0x7c9c0000 - 0x7d1d5000      C:\WINDOWS\system32\shell32.dll
0x77f60000 - 0x77fd6000      C:\WINDOWS\system32\SHLWAPI.dll
0x773d0000 - 0x774d2000      C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.2180_x-ww_a84f1ff9\comctl32.dll
0x5d090000 - 0x5d127000      C:\WINDOWS\system32\comctl32.dll
0x605d0000 - 0x605d9000      C:\WINDOWS\system32\mslbui.dll
0x77120000 - 0x771ac000      C:\WINDOWS\system32\OLEAUT32.DLL
0x6d530000 - 0x6d543000      C:\Program Files\Java\jdk1.5.0_07\jre\bin\net.dll
0x71ab0000 - 0x71ac7000      C:\WINDOWS\system32\WS2_32.dll
0x71aa0000 - 0x71aa8000      C:\WINDOWS\system32\WS2HELP.dll
0x6d550000 - 0x6d559000      C:\Program Files\Java\jdk1.5.0_07\jre\bin\nio.dll
0x6d230000 - 0x6d253000      C:\Program Files\Java\jdk1.5.0_07\jre\bin\dcpr.dll
VM Arguments:
java_command: writingplatform.Main
Launcher Type: SUN_STANDARD
Environment Variables:
CLASSPATH=C:\Program Files\Java\jre1.5.0_05\lib\ext\QTJava.zip
PATH=C:\Program Files\Microsoft DirectX 9.0 SDK (August 2005)\Utilities\Bin\x86;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\ATI Technologies\ATI Control Panel;C:\Program Files\QuickTime\QTSystem\;C:\Program Files\SSH Communications Security\SSH Secure Shell
USERNAME=Wanderer
OS=Windows_NT
PROCESSOR_IDENTIFIER=x86 Family 15 Model 2 Stepping 9, GenuineIntel
--------------- S Y S T E M ---------------
OS: Windows XP Build 2600 Service Pack 2
CPU:total 2 family 15, cmov, cx8, fxsr, mmx, sse, sse2, ht
Memory: 4k page, physical 1047764k(366012k free), swap 2518724k(2059484k free)
vm_info: Java HotSpot(TM) Client VM (1.5.0_07-b03) for windows-x86, built on May 3 2006 01:04:38 by "java_re" with MS VC++ 6.0

This is not your bug, it's Sun's. All you can do is to:
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
On the other hand, if you cannot afford to wait and just
want to find a quick workaround, you will at least need
to find a way to reproduce the bug with a reasonable
frequency. If you are absolutely unable to reproduce it,
just forget it, but still report it to Sun.

Switching from Microsoft JVM to sun JVM plugin. Problem w crystal reports

Hi,
I am currently in the process of switching off of the microsoft jvm to the sun plugin. I am using the reportviewerbean to view the reports. This works fine in the microsoft JVM, but I am getting a server not found error in the java JVM plugin. Here is the codes that is currently used:
bean = new ReportViewerBean();
if ( reportname.startsWith("/") )
java.net.URL url = this.getDocumentBase();
reportname = url.getProtocol() + "://" + url.getHost() + ":" + url.getPort() + reportname;
add((Component) bean);
((Component) bean).setBounds(0, 0, (int)this.getSize().width, (int)this.getSize().height);
bean.start();
bean.setBackground(Color.gray);
bean.setPromptOnRefresh(false);
bean.setHasGroupTree(false);
bean.setHasPrintButton(true);
//setZoomFactor(100);
bean.setZoomFactor(-2);
Log.debug("In report viewer: setting report parameters: "+reportparameters);
bean.setReportParameter(reportparameters);
* It's important to set the report name last. This tells the Crystal viewer to
* start the report. Otherwise you can get multiple URL requests for the same report.
Log.debug("In report viewer: setting reportname: "+reportname);
bean.setReportName(reportname);
Can anyone tell me what I am doing wrong or what I need to do differently for the SUN environment
Thanks

Hi
I have started playing with this again my full msg is:
Crystal Report Viewer 1.3.7
java.vendor = Sun Microsystems Inc.
java.version = 1.6.0_05
os.arch = x86
os.version = 5.1
File name = java_plugin1.epf
"java_plugin1.epf" does not exist.
No response from server.
URL = http://localhost:7001/cis/servlets/reports/mgnt/WorkflowDetailReport1.rpt?viewer=java&vfmt=encp&vgen=652&language=en
Parameters = viewer=java_plugin&cmd=get_pg&ttl_info=&page=1&incomplete_page=1&incomplete_page_count=1&pversion=3&promptOnRefresh=0
network: Connecting http://localhost:7001/cis/servlets/reports/mgnt/WorkflowDetailReport1.rpt?viewer=java&vfmt=encp&vgen=652&language=en with proxy=DIRECT
Failed to connect to server.
I have noticed that the viewer is set to equal java and not java_plugin. I am wondering if this is the problem. does anyone know how to change the viewer= ?
thanks,
Marc

Microsoft JVM & Sun JVM

I have the Sun JVM 1.3 and 1.4 installed on my computer.
IE is set to use the sun JVM (1.4) for the <APPLET> tag (in tool->Internet Options->Advanced).
How can I launch an applet using the Microsoft JVM ?
I have try something like:
<object classid="08B0E5C0-4FCB-11CF-AAA5-00401C608500"
width=150 height=150>
<param name=codebase value="http://www.blabla.com/here">
<param name=code value="JavaClass.class">
</object>
But my IE keep craching.
Any help ?

Well in fact I have found a solution, but I don't know if it's full proof, does somebody have any idea ?
I use:
<object classid="java:MyCode.class"
codetype="application/java"
width=my_width
height=my_height>
<param ....>
</object>

How To: Debug missing Drivers in MDT

The definitive post on missing drivers in MDT (most comprehensive list I've done so far)…
Please to NOT post questions from this thread, instead create a new thread.
How to debug Network Driver Problems
One of the earliest hurdles an MDT administrator will come across is the management of device drivers, specifically networking drivers. With most other drivers, like Audio, printer, and video drivers, a quick call to Windows Update or install over the network
will resolve the Installation. However unless the Network (and storage) Drivers are installed into Windows from the start, it will be much more difficult to install the rest of the system.
This post should help you get started if you find a machine that did not install a device driver properly, and you want to know how to find and import the correct drivers.
Installing network drivers in the
full OS
Step 1 - Try network connection again
It's possible that you might get a DHCP error from MDT, but when you try again later to connect the Deployment Share it works! This may be caused by a slow or malfunctioning DHCP server in your network. Re-check your DHCP servers, ensure that PortFast is enabled
on your routers. If all else fails get your network administrators to document the DHCP delay. A long delay in modern networks is unnecessary.
Step 2 - Verify connectivity
You may not have a driver problem but a network problem. Check the physical connection on the computer (Network installs on MDT *REQUIRE* a wired network connection, no Wi-Fi). Open a web browser. Check the IP Address (ipconfig.exe /all). Ping the Deployment
Server, manually connect to the Deployment Share. IF you can't connect to the Deployment Share, neither can MDT.
Step 3 - Find the Correct Driver Package
Before you load the driver into MDT, first verify that you have the correct driver. There are scenarios where you may *think* you have the correct driver, but the driver will never run because the package is designed for a different OS/SKU/Platform/whatever.
Install the driver package by:
  ○ Open the Device Manager (devmgmt.msc).
  ○ Find the network device in the list (ensure this is the wired device, not the wireless device)
  ○ Right click on "Properties" and click on the "Details" tab.
  ○ From the "Details" tab, select the property "Hardware Ids" select all the values, and copy to the clipboard, it would be a good idea to save for later. Should look something like:
      PCI\VEN_8086&DEV_1502&SUBSYS_21F317AA&REV_04
      PCI\VEN_8086&DEV_1502&SUBSYS_21F317AA
      PCI\VEN_8086&DEV_1502&CC_020000
      PCI\VEN_8086&DEV_1502&CC_0200
  ○ From the "Driver" tab, click on "Update Driver…", click on "Browse my computer for driver software" locate the driver package on the local machine or USB Drive, and install the package.
  ○ You should get a confirmation that the driver package was installed.
  ○ IF you do not get confirmation, MDT driver installation may not work.
Windows will install the driver starting with the *.inf install package, and will typically include a *.sys (binary) and a *.cat (digital Signature). If the driver package has been re-packaged into a *.cab, *.zip, or other compressed *.exe file, the
package must be extracted first. This is a hard requirement for any driver used by MDT and/or SCCM. All driver packages that are signed by Microsoft (WHQL) will be installed from the *.inf file, and you should only use devices that have the Microsoft WHQL
Logo as a sign of quality.
If you need a help on where to find driver packages for your devices, the 3 largest Computer OEM manufacturers supply drivers grouped by Make and Model that are easily imported into MDT and SCCM. See:
http://deploymentbunny.com/2014/07/08/back-to-basicwhere-to-find-drivers-for-servers-and-clients/
Step 4 - Load driver into MDT
If you have more than 20 driver packages, or if you anticipate you will have more than 20 drivers, you should start grouping your drivers in sub-folders for organization. One popular method is to group by Computer Make and Model. Ensure that you are using the
correct Driver Selection Profile in your task sequence. If you are unsure, disable any selection profile(s) to ensure the driver is installed correctly.
Step 5 - Run the full MDT installation
During installation MDT will perform the following:
  ○ Run the PNPEnum.exe utility and capture output to PnPEnum.xml. The VEN_Xxxx and DEV_Yyyy from the "HardwareIDs" property above must be present in this list. Otherwise we won't have a match.
  ○ Search through the %DeployRoot%\control\drivers.xml file looking for a match for the HardwareID. MDT may filter the search based on the folder search type.
  ○ MDT will copy each matching driver to the local c:\drivers directory using the xcopy.exe command. You can search (grep) for the string "xcopy" in the ZTIDrivers.log file, that will get you list of all driver packages matched by MDT.
  ○ MDT will allow the machine to boot into the NEW OS, and Driver Installation will begin in the OS. IF there are multiple drivers found and copied locally, the Windows (not MDT) will determine the best one. The c:\windows\inf\SetupAPI.*.log files
will detail which drivers copied locally were installed (or *not* installed).
Installing Network Drivers in
WinPE
Step 6 - Try the network connection again
(See above
Step 7 - Verify Connectivity from within WinPE
Verifying network connectivity will be a bit more difficult in WinPE, since we have a limited User Interface, so all investigation must be done in the debugging mode (Press F8) cmd.exe
  ○ Try connecting to the Deployment Share:
  c:\> net use * \\MDT\DeploymentShare$ /u:UserDomain\UserName *
  ○ Try pinging the Deployment Server:
  c:\> Ping.exe MDT.Corp.contoso.com
  ○ Verify that you have an IP address ( ipconfig /all ) If you have an AutoConfiguration address - Driver OK - WinPE can't reach the DHCP server. If you have "Media Disconnected" - Driver OK - Physical adapter not plugged to network. If
no devices are listed - Driver bad - Driver not installed.
  ○ Check the x:\windows\system32\WpeInit.log - This log will show the network driver (if found) being installed.
Step 8 - Verify driver packages are getting included into WinPE
Firstly, verify the correct driver package from within the full OS above. By default MDT will import *all* Storage and Networking drivers into your WinPE image. However it is possible to change the subset of files copied via "Selection Profile" or
other method. Cross check your WinPE Driver Settings.
  ○ From within the MDT console, right click on the root of your Deployment Share and select properties.
  ○ Click on the "Windows PE" tab, and the "Drivers and Patches" sub tab for both x86 and x64.
  ○ Your Network Drivers package must be in the "Selection Profile" if enabled.
Finally verify that the correct Network Driver package is being copied to WinPE. If necessary this may include setting up a debugger to watch the MDT Provider build the WinPE Image from scratch. My preference is to use the SysInternals
http://live.sysinternals.com/Dbgview.exe tool.
  ○ Open up the MDT console.
  ○ Download and run the DbgView.exe tool.
  ○ Update the deployment share in question.
  ○ The DbgView tool should show what drivers were copied to each WinPE Image.
Other
Whenever you add a driver into the MDT console, you must update the deployment share for that drivers to be added to your WinPE Image. If you are unsure, select "Completely regenerate the boot images." to ensure the drivers is imported. Additionally,
you must copy the updated LitetouchPE_x??.wim and *.iso files to the other consumers of the WinPE image like WDS/PXE and or any USB offline media.
Note that some Broadcom NetXtreme class of drivers have a multi-function driver architecture that may have difficulty loading in WinPE. Ensure that you load the "RIS" class of drivers from Broadcom in your MDT environment.
Note that by default MDT does *NOT* support the installation of Windows over Wireless network devices (Wi-Fi). The MDT installation sources must either be available through wired networking, or offline (USB Flash) media.
This post does not discuss origination of drivers within MDT ( Chaos vs. Total Control ), that is a different topic.
http://www.deploymentresearch.com/Research/tabid/62/EntryId/112/MDT-2013-Lite-Touch-Driver-Management.aspx
Further Help
If you are still having problems with drivers in via MDT, ask the experts in the MDT Technet Forum:
Include a short description of the problem. Including the Make/Mode if necessary.
Include the HardwareIDs from the Device Manager (Devmgmt.msc) into the post (from above).
Copy your known good driver package (step 3 above) to OneDrive.
Copy the following log files to a public site like OneDrive and include the link:
  ○ PnpEnum.xml (from Client)
  ○ Bdd.log (From Client) - or at least the ZTIDrivers.log file.
  ○ c:\windows\inf\SetupAPI.*.log (from client)
  ○ %DeployRoot%\control\Driver*.xml
  ○ %DeployRoot%\control\SelectionProfile*.xml
  ○ %DeployRoot%\control\settings.xml (if problems in WinPE)
  ○ x:\windows\System32\WpeInit.log (if problems in WinPE)
  ○ If the MDT server is not including your driver package in WinPE include the DBGView log.
This post is by Keith Garner - Keith was a developer on the MDT team where he developed the ZTIDrivers.wsf script, he also worked for the Windows Hardware Quality Labs as a technical PM on Driver Quality, and developed samples for the
Microsoft Device Driver Kit (DDK) specifically around the area of Device Driver installation in the OS (Windows NT 5.0, 2000 and Windows XP). (So yes, I know drivers :^).
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

OK. I have redone the drivers for WinPE which has reduced the image size by about 200MB. Unfortunately the problem persists.
Is there anyway to turn on some sort of boot logging so I can see what driver it is failing on?
I am also still seeing the weird behavior of it working over PXE but blue screens when booting from USB. Can anyone explain that?
JJ

Problem to debug applet, please help...

i use windows.
there are 3 files under "c:\current" directory, they are
file 1. mem_appletviewer.bat - with content:
"e:\install\java\jdk1.3.1_05\bin\appletviewer" -J-Xdebug -J-Xrunjdwp:transport=dt_shmem,address=conn001122,server=y,suspend=y test.htm
file 2. mem_jdb.bat - with content:
"e:\install\java\jdk1.3.1_05\bin\jdb" -attach conn001122
file 3. test.htm - with applet tag:
<applet
code="Let0.class"
codebase="G:\Victor\Vc5060\Develop\JCity\files\RecentFile"
width=400 height=250 ></applet>
(Let0.class is a simplest class extends Applet)
please note, codebase is not "c:\current" directory
problems happend when i debug: (run mem_appletviewer.bat first then mem_jdb.bat)
a) if move Let0.class to "c:\current" directory, debug is fine but test.htm can not load Let0.class itself because of codebase tag.
b) if move Let0.class to codebase directory (G:\Victor\Vc5060\Develop\JCity\files\RecentFile), test.htm can load the class but appletviewer can not load the class (can not find Let0.class).
===========================================================
in my application, i need to put Let0.class in codebase directory.
Question:
1) how to set -classpath for appletviewer (as debug application class in java.exe )? is it possible?
2) codebase TAG in test.htm doesn't work for appletviewer, what is problem? how to fix it?
totally:
how to debug Let0.class if it is in codebase directory (not in "c:\current")?
thx

i fix it.

Debug applet embedded in jsp using tomcat and eclipse

I am trying to debug applet embeded in jsp. I have deployed my application on tomcat.
The steps I followed
1. Added JVM rumtime parameters in Java plugin control panel
-Djava.compiler=NONE -Xnoagent -Xdebug -Xrunjdwp:transport=dt_socket,address=localhost:8000,suspend=n
2. Added JPDA_ADDRESS = localhost:8000 and JPDA_TRANSPORT=dt_socket to catlina.bat
3. I start my server from commandline prompt "catalina.bat JPDA start"
4.I have made a new configuration for remote debug in eclipse debug>new> connection type (socket attach) >port 8000
5. when I open my application url in browser browser closes and command prompt displays "*Debugger failed to attach , timeout before handshake*"
Any help on this ?
Thanks in advance

Personally, I have no knowledge about Applet but have you checked this link?
[http://blogs.sun.com/thejavatutorials/entry/deployment_toolkit_101|http://blogs.sun.com/thejavatutorials/entry/deployment_toolkit_101]

How to debug this error? trying to load excel file to Database

SSIS package "c:\users\asubedi\documents\visual studio 2012\Projects\Integration Services Project1\Integration Services Project1\PackageToLoadBuyerDedupe.dtsx" starting.
Information: 0x4004300A at BuyerDedupe, SSIS.Pipeline: Validation phase is beginning.
Error: 0xC0209303 at PackageToLoadBuyerDedupe, Connection manager "Excel Connection Manager": The requested OLE DB provider Microsoft.ACE.OLEDB.12.0 is not registered. If the 64-bit driver is not installed, run the package in 32-bit mode. Error code: 0x00000000.
An OLE DB record is available. Source: "Microsoft OLE DB Service Components" Hresult: 0x80040154 Description: "Class not registered".
Error: 0xC001002B at PackageToLoadBuyerDedupe, Connection manager "Excel Connection Manager": The 'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine. For more information, see http://go.microsoft.com/fwlink/?LinkId=219816
Error: 0xC020801C at BuyerDedupe, Excel Source [2]: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "Excel Connection Manager" failed with error code 0xC0209303. There may be error messages posted before this with more information on why the AcquireConnection method call failed.
Error: 0xC0047017 at BuyerDedupe, SSIS.Pipeline: Excel Source failed validation and returned error code 0xC020801C.
Error: 0xC004700C at BuyerDedupe, SSIS.Pipeline: One or more component failed validation.
Error: 0xC0024107 at BuyerDedupe: There were errors during task validation.
SSIS package "c:\users\asubedi\documents\visual studio 2012\Projects\Integration Services Project1\Integration Services Project1\PackageToLoadBuyerDedupe.dtsx" finished: Failure.
how to debug this issue?

Hi Arjunji,
The issue occurs because you have only 32-bit Microsoft ACE 12.0 OLEDB drivers installed, however, the package runs in 64-bit runtime mode which requires 64-bit drivers.
To avoid this issue, you need to either install the 64-bit
Microsoft Access Database Engine 2010 Redistributable or run the package in 32-bit runtime mode. To run the package in 32-bit runtime mode, in SSDT, you can set the Run64BitRuntime property of the IS project to False; in a SQL Server Agent job, you can
configure the SSIS Package Job step and check the “Use 32 bit run time” option.
In addition, please note that the 32-bit install file of Microsoft Access Database Engine 2010 Redistributable and the 64-bit one cannot be installed side by side on a single server. However, if your current ACE 12.0 OLE DB drivers are installed by 32-bit
Office suit, you can go ahead and install the 64-bit Microsoft Access Database Engine 2010 Redistributable.
Regards,
Mike Yin
TechNet Community Support

Problem on debug Applet

hi all,
i am developing an user debugger which is used to debug Applet.
problem is, the Applet debugged must be in same directory as the debugger, simply says, the command must be:
appletviewer MyApplet
or
java sun.applet.AppletViewer MyApplet
i need following command work:
appletviewer file:/c:\folder\MyApplet
because normally debugger is not in the same directory as Applet debugged.
how to solve the problem?
i guess i have to develop my own AppletViewer, but how to do?
thx

i fix it.

HOW TO: Debug a remote JSP

<h1>HOW TO: Debug a remote JSP</h1>
Note: The process of debugging a remote JSP on an Apache/Jserv
installation involves a couple extra steps that were not covered in the JDeveloper
3.2 documentation. 
Introduction
You use JDeveloper to debug JavaServer Pages (JSP) deployed and running on
a server that includes a JSP container, such as Apache Jserv. Your JSP container
will need to be configured to enable remote JSP debugging using JDeveloper.
JDeveloper allows you to use one of two protocols for JSP debugging - the
Oracle Java Virtual Machine (OJVM) debugging protocol or the Sun Java Platform
Debugging Architecture (JPDA). Before you start your remote debugging session,
you will have to choose which method to use. If you use the OJVM protocol, your
debugging session will run more quickly and you will have some additional features
to assist you. You can only use OJVM on a Windows NT system. If your server
is running UNIX or another operating system, you must use the
"classic" JVM.
Setting up your project for remote JSP debugging
Once you have created a JSP project, you need to set your project options
so that remote debugging is enabled: 
<ol>
From the Project menu, select Project
Properties. 
</li>
Click the Run/Debug tab.
</li>
From Debug Files As: dropdown list, select Remote
Debugging. 
</li>
Click OK. 
</li>
</ol>
Configuring the Remote Server
The following options must be changed on the host running the Apache/Jserv
server. These instructions assume the server is running Windows NT: 
Changes to jserv.properties
These options control which Java Virtual Machine is used and how it is loaded.

<ol>
For The Java Virtual Machine interpreter parameter <tt>wrapper.bin</tt>:

</li>
<ul>
[*]Comment out any existing entries by putting a <tt>#</tt> at the beginning
of the line.
<blockquote>
<pre>#wrapper.bin=C:\java1.1.8\bin\java.exe</pre>
</blockquote>
</li>
[*]Add a new entry with the full path of the <tt>java.exe</tt> that you want
to use. To use the JDeveloper 1.3 OJVM, put
<blockquote>
<pre>wrapper.bin=C:\Program Files\Oracle\JDeveloper 3.2\java1.2\bin\java.exe</pre>
</blockquote>
</li>
</ul>
For the Arguments passed to Java interpreter parameter <tt>wrapper.bin.parameters</tt>:
The value you put for this parameter depends on which Debugging Protocol
you will choose in the Remote Debugging Dialog in JDeveloper
when you start debugging.
</li>
<ul>
[*] If you want to use the JDeveloper 3.2 OJVM, put </li>
<blockquote>
<pre>wrapper.bin.parameters=-ferrari -XXdebugondemandquietport4000</pre>
</blockquote>
[*]If you want to use Java Platform Debugging Architecture, put
<blockquote>
<pre>wrapper.bin.parameters=-classic -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=4000 -Xdebug -Xnoagent -Djava.compiler=NONE</pre>
</blockquote>
The <tt>4000</tt> parameter defines the port number which the JDeveloper
debugger will use to communicate with the server. You can specify a different
port number, but it must match the port which you will enter in the Remote
Debugging Dialog in JDeveloper when you start debugging. 
</li>
</ul>
[*] For the PATH environment value passed to the JVM parameter <tt>wrapper.path</tt>
enter the location of <tt>jdwp.dll</tt>, which is part of the Java Platform
Debugging Architecture.
This parameter is only necessary if you will choose the Java Platform
Debugging Architecture debugging protocol:
<blockquote>
<pre>wrapper.path=C:\jpda\bin</pre>
</blockquote>
</li>
For the CLASSPATH environment value passed to the JVM parameter
<tt>wrapper.classpath</tt>: 
<ul>
Keep the location of <tt>ApacheJServ.jar</tt>. If it is not already
there, add it. 
<blockquote>
<pre>wrapper.classpath=C:\Program Files\Apache\JServ\ApacheJServ.jar</pre>
</blockquote>
</li>
Comment out the location of <tt>jsdk.jar</tt>. 
<blockquote>
<pre>#wrapper.classpath=C:\jsdk2.0\lib\jsdk.jar</pre>
</blockquote>
</li>
[*]Add the location of <tt>servlet.jar</tt> from JDeveloper 3.2.
<blockquote>
<pre>wrapper.classpath=C:\Program Files\Oracle\JDeveloper 3.2\lib\servlet.jar</pre>
</blockquote>
</li>
[*] Add the locations of <code>jdeveloper.zip</code> and <code>ojsp.jar</code>
from JDeveloper.
<blockquote>
<pre>
wrapper.classpath=C:\Program Files\Oracle\JDeveloper 3.2\lib\jdeveloper.zip
wrapper.classpath=C:\Program Files\Oracle\JDeveloper 3.2\lib\ojsp.jar
</pre>
</blockquote>
</ul>
</ol>
Changes to jserv.conf
<ol>
For the ApJServAction parameter: 
<ul>
[*] Comment out any existing <tt>ApJServAction .jsp</tt> entries by putting
a <tt>#</tt> at the beginning of the line. </li>
<blockquote>
<pre>
#ApJServAction .jsp /servlets/org.gjt.jsp.JSPServlet
</pre>
</blockquote>
[*]Add a new <tt>ApJServAction .jsp</tt> entry like this.
<blockquote>
<pre>
ApJServAction .jsp /servlets/oracle.jsp.JspServlet
</pre>
</blockquote>
</li>
</ul>
</li>
</ol>
Changes to zone.properties
<ol>
In the Servlet Init Parameters section: 
</li>
<ul>
Add the following lines. 
<pre>
servlet.oracle.jsp.JspServlet.initArgs=emit_debuginfo=true
servlet.oracle.jsp.JspServlet.initArgs=jspcompiler=oracle.jdeveloper.jsp.JspOjcCompiler
servlet.oracle.jsp.JspServlet.initArgs=classpath=C:\Program Files\Oracle\JDeveloper 3.2\java1.3\jre\lib\rt.jar
</pre>
</li>
</ul>
</ol>
Copying the JSP to the Apache/Jserv Server
Once you have restarted the server with the modified parameters, you need to
copy your JSP to the server's HTML root directory. For most Apache installations
this is <tt>C:\Program Files\Apache\htdocs</tt>. 
You also need to make sure the JSP is in your HTML directory in the JDeveloper
tree, typically <tt>C:\Program Files\Oracle\JDeveloper 3.2\myHTML</tt>. The
reason for this is JDeveloper uses the folder name as its package name.
Debugging a JSP
Debugging a JSP is very similar to debugging any other Java program.
<ol>
From the Run menu, select Debug
"filename.jsp". 
Start the JSP running (for example, start your web browser and open a
connection to the JSP). 
Debug as normal. 
</ol>
If you are using the JDeveloper OJVM debugging protocol, you will be able
to disconnect from the JSP container. This allows you to stop debugging, but
leave the JSP container running. In addition, you will be able to use two extra
debugging functions that are not available using the JDPA protocol - Run
to End of Method and Set Next Statement.
If you using JPDA, you must use Stop to end your debugging.
Using this method will also stop the JSP container.
<blockquote>

</blockquote>
null

Hi,
It again same as you do in your local server...You can monitor the BPEL process flow in the em console and debug..if its not sufficient....u can also monitor the logs located at
<SOA_Home>\user_projects\domains\domain1\servers\soa_server1\logs to debug.

Sun Plug-In vs. Microsoft JVM

I'm looking for current percentages as to how many systems have Sun Plug-In vs. Microsoft JVM installed. Creating an application in which I want to force the end-users to use the Sun Plug-In but I need the current percentages to help convince my customer. If anyone knows of a site where I can find this information, would be much appreciated.

I don't know percentages but if you will have users on Windows XP or Longhorn, you can forget about using the Microsoft JVM cause it won't be there. Since you are creating a new application, I think it is a no-brainer to use Sun. In fact, Microsoft has published guides on transitioning away from the Microsoft JVM - see http://www.microsoft.com/mscorp/java/

How to debug applet on Microsoft JVM

Similar Messages

Maybe you are looking for