Creating Screen Caps
Can anyone help me to create a screen cap from one of my films and use that as a picture file. I have found how to create a freeze frame but is there a way to turn that freeze frame into a picture file or a screen cap . And Im not sure if its easier to do this in Motion instead. Any help is appreciated.
Welcome to the forum.
I have no idea why you, and others, insist upon thinking that it is necessary to make a freeze frame, before exporting a still.
With NO in or out points on the timeline, place the playhead on the frame you wish to export.
File>Export> QT Conversion> Still image> chose your flavor.
Similar Messages
-
Screen-caps - A Photoshop Workflow
Users often ask how to do screen-caps, to show what is happening with their program. Below are possible workflows for creating the screen-caps, and then there are instructions on how to "attach" the screen-caps to a Reply in the Adobe Forums, but only if one is accessing them via a Web browser - with e-mail access, you cannot attach a screen-cap, or other image file. There are first several utilities that will help you do this, but I will outline the steps using Adobe Photoshop and the Windows Clipboard. One can substitute their image editing program of choice, such as Photoshop Elements, PaintShop Pro, or other.
Windows has a Clipboard feature, and one can use the Print Screen key (often seen as Prt Sc, etc., and depending on their computer, might have to also use a modifier key, such as the Ctrl key).
First, set up your program, so that the necessary items are shown. This might be zooming in on the Timeline, even expanding it vertically, moving the CTI (Current Time Indicator with the red Edit Line attached), and perhaps selecting a problem Clip. Often, the Program Monitor will also need to be seen, and perhaps the Project Panel showing the proper Asset, or maybe the Effects Control Panel. Get these setup, so that they are visible, and where you want them. Now, hit the Print Screen key (see above for comments). The screen will now be an image in Clipboard.
Open your image editing program. Here, I’m using Photoshop. Create a New Image. Photoshop will first look in the Clipboard, and if there is an image there, will even set up your New Image to match that w/ the proper pixel x pixel size. Here, I name that New Image with a name that means something to me, like, “PrE_Audio_Mixer_01.” I use the underscore, in lieu of spaces, as the forum software sometimes has problems with file names containing spaces. Yes, I know that this is so Windows 98, but it works well for me.
Hit Ctrl+V to Paste the image from the Clipboard into this New Image. If my full screen-cap has captured more image area, than I need, I Crop to the important parts.
Next, if I need to do call outs, or annotate the image, I use the Text Too, and maybe will draw boxes, or circles, to make sure that the viewer knows exactly where I want them to look and what to look for. To draw arrows, or lines, I use the Shape Tool, and/or the Pen Tool, and Stroke, or Fill these Paths, as is necessary.
At this point, I have a Layered file with drawings and text, overlaying my screen image. I will do a Save_As and choose .PSD to keep my Layers handy for any additional editing, if necessary. The one problem is that the Adobe forum will NOT attach a .PSD file. Here, one has several choices. One is to do a Save_for_Web, and let PS Flatten the Layers, and merge them into one Layer. That will also remove any Alpha Channels, and/or Paths. Two popular formats are .PNG, or JPEG, and Save_for_Web allows for either of these. The choice is yours, but I normally just use JPEG with a Quality of about 9, in Photoshop to compress the image, but still leave it sharp enough for others to read. Again, PNG is a good choice as well, and will yield slightly better quality for the file size. Only possible issue is that many older browsers (what the viewers will be using to view the screen-cap) do not handle PNG. All newer browsers do, and do so very well. I have begun using PNG, instead of any compression of JPEG, and the results are better, and sharper.
With the screen-cap image Saved to our HDD, I use the little “camera” icon, in the lower-middle of the Adobe Forum editing screen’s Toolbar, to actually attach the image:
Here is an example of a screen-cap with the program setup as I needed, call outs and annotations:
Hope that this helps. Note: other image editing programs will differ, as will various screen-cap utilities.
Good luck,
HuntNeale,
Thanks for that. I had never used Alt+Prt Scr on my Sager, and did not know of the specifics of that modifier key. On my laptop, I need to do Ctrl+Prt Scr, rather than the more common Prt Scr (no modifier key), but that is fairly specific to my Sager on the Clevo MoBo, with its keyboard. On many computers, just plain Prt Scr is all that's needed.
I'll experiment with Alt+Prt Scr, as that might actually save me a Crop in PS, when doing a screen-cap.
Thanks,
Hunt -
Placing Images (Screen Caps) for Callouts - Best Practice?
Illustrator CS6, Windows 7
I'm placing screen captures (screen images from software) in my artwork files to add callouts and create illustrations for a user manual.
The machine I'm capturing on has a screen resolution set at 1920 x 1080 (required for software). I'm using Snagit and capturing the screens, saving files, then placing in Illustrator. I've been using images minimum 300 dpi and never upsizing in Illustrator. Still I think my results could be better.
In the past I've used .jpg as my export filetype for placing into Illustrator. But, recent reads of postings in this community lead me to believe my practice might be flawed.
Question: What is considered best practice for placing images from screen capture (or any source) in Illustrator? What file type from capture will get me the clearest and most adaptable results?
My Illustrator file color mode is CMYK and my other art and callouts supporting the screen cap are working great.
I'm creating the artwork for import to Framemaker and creating a PDF for online and print.What I mean is; what is the user looking at, and what are you training on?
For example, if the application involves medical imaging, and part of your documentation covers something like evaluating medical images in the application, that would probably be a far more color-critical scenario than an application in which the user just views and manipulates data.
Generally, you don't need anything like 300 PPI for screen captures in software documentation. The whole intent is for the image to look like the screen you are documenting, which is something like 72 or 96 PPI at actual size. You might downscale a screen capture as much as 50%, but at that size, the reader is viewing the application's text (including menus, etc.) at half the size as viewed in the application, which is assumed to be sized for comfortable reading. Sharpness is good. You don't want the images to become blurred in pursuit of completely needless "resolution."
Also generally speaking, software screenshots are not usually color-critical. Placing (even pasting from SnagIt) directly into the page layout app is usually just fine. PostScript knows how to separate RGB images. Such things have been done since long before anyone sweated blood over "color management." Assuming your application interface is not using garish color (which would be poor interface design; it's tiring), I dare say the conversion of RGB screenshots to CMYK at the imagesetter or press would be fine.
How is the manual going to be printed? Unless you're talking about a large press runs, nowadays software documentation (subject to frequent updates) is often printed on on-demand presses (think glorified digital color copiers), not sheetfed presses. With software documentation, you're not usually talking coffee-table collector's books. (The exception would be something like a book on color-correction in Photoshop; thus my first question.)
I routinely paste screenshots from SnagIt directly into InDesign pages to document software applications, and add the callouts in InDesign. Only when I need some special graphics (swooping arrows, etc.) do I assemble the callouts to the screenshots in Illustrator; and even when I do that, I also typically paste the SnagIt captures directly in to AI.
Keeping your callouts native to the page layout program also better facilitates language translation, when you have to outsource that.
JET -
Startx on a vmware is throwing a "failed to create screen resources"
The Bottom line error is:
Fatal server error:
[ 1431.076] (EE) failed to create screen resources(EE)
I am trying to get a browsers running on my new Arch Linux, so I can cut and paste better for questions. I have installed xorg, chromium, firefox. If I try and start "startx", it say the server did not start. I think it is the failed to create screen resources.
I have edit the video settings to give it 32meg of memory. Also I hack the .vmx file to enable the 3d opttion. I have installed all the vmtools (open version) Again, new to Arch Linux so I sure it is something stupid.
Not sure if it helps but here are the errors when I try and run the browsers.
chromium
[320:320:1121/142755:Error:browser_main_loop.cc(209) Gtk: cannot open display:
firefox
(process:354): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
Error: no display specified
Entire log Xorg.0.log
[ 1430.963]
X.Org X Server 1.16.2
Release Date: 2014-11-10
[ 1430.965] X Protocol Version 11, Revision 0
[ 1430.965] Build Operating System: Linux 3.17.2-1-ARCH x86_64
[ 1430.967] Current Operating System: Linux PingBuild 3.17.3-1-ARCH #1 SMP PREEMPT Fri Nov 14 23:13:48 CET 2014 x86_64
[ 1430.967] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=36544952-8a9a-41c9-b169-87189310b752 rw quiet
[ 1430.969] Build Date: 10 November 2014 07:52:13PM
[ 1430.970]
[ 1430.970] Current version of pixman: 0.32.6
[ 1430.972] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 1430.972] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 1430.975] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Nov 21 12:53:21 2014
[ 1430.976] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 1430.976] (==) No Layout section. Using the first Screen section.
[ 1430.976] (==) No screen section available. Using defaults.
[ 1430.976] (**) |-->Screen "Default Screen Section" (0)
[ 1430.976] (**) | |-->Monitor "<default monitor>"
[ 1430.976] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 1430.976] (==) Automatically adding devices
[ 1430.976] (==) Automatically enabling devices
[ 1430.976] (==) Automatically adding GPU devices
[ 1430.976] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[ 1430.976] Entry deleted from font path.
[ 1430.976] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/OTF/,
/usr/share/fonts/100dpi/,
/usr/share/fonts/75dpi/
[ 1430.976] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 1430.976] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 1430.976] (II) Loader magic: 0x818d80
[ 1430.976] (II) Module ABI versions:
[ 1430.976] X.Org ANSI C Emulation: 0.4
[ 1430.976] X.Org Video Driver: 18.0
[ 1430.976] X.Org XInput driver : 21.0
[ 1430.976] X.Org Server Extension : 8.0
[ 1430.979] (II) systemd-logind: took control of session /org/freedesktop/login1/session/c1
[ 1430.979] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 1430.983] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 8 paused 0
[ 1431.010] (--) PCI:*(0:0:15:0) 15ad:0405:15ad:0405 rev 0, Mem @ 0xd8000000/67108864, 0xd0800000/8388608, I/O @ 0x000010d0/16, BIOS @ 0x????????/32768
[ 1431.010] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 1431.010] (II) LoadModule: "glx"
[ 1431.011] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 1431.016] (II) Module glx: vendor="X.Org Foundation"
[ 1431.016] compiled for 1.16.2, module version = 1.0.0
[ 1431.016] ABI class: X.Org Server Extension, version 8.0
[ 1431.016] (==) AIGLX enabled
[ 1431.016] (==) Matched vmware as autoconfigured driver 0
[ 1431.016] (==) Matched vmware as autoconfigured driver 1
[ 1431.016] (==) Matched modesetting as autoconfigured driver 2
[ 1431.016] (==) Matched fbdev as autoconfigured driver 3
[ 1431.016] (==) Matched vesa as autoconfigured driver 4
[ 1431.016] (==) Assigned the driver to the xf86ConfigLayout
[ 1431.016] (II) LoadModule: "vmware"
[ 1431.017] (II) Loading /usr/lib/xorg/modules/drivers/vmware_drv.so
[ 1431.044] (II) Module vmware: vendor="X.Org Foundation"
[ 1431.044] compiled for 1.16.0, module version = 13.0.2
[ 1431.044] Module class: X.Org Video Driver
[ 1431.044] ABI class: X.Org Video Driver, version 18.0
[ 1431.044] (II) LoadModule: "modesetting"
[ 1431.044] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[ 1431.044] (II) Module modesetting: vendor="X.Org Foundation"
[ 1431.044] compiled for 1.16.0, module version = 0.9.0
[ 1431.044] Module class: X.Org Video Driver
[ 1431.044] ABI class: X.Org Video Driver, version 18.0
[ 1431.044] (II) LoadModule: "fbdev"
[ 1431.045] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[ 1431.045] (II) Module fbdev: vendor="X.Org Foundation"
[ 1431.045] compiled for 1.16.0, module version = 0.4.4
[ 1431.045] Module class: X.Org Video Driver
[ 1431.045] ABI class: X.Org Video Driver, version 18.0
[ 1431.045] (II) LoadModule: "vesa"
[ 1431.045] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[ 1431.045] (II) Module vesa: vendor="X.Org Foundation"
[ 1431.045] compiled for 1.16.0, module version = 2.3.2
[ 1431.045] Module class: X.Org Video Driver
[ 1431.045] ABI class: X.Org Video Driver, version 18.0
[ 1431.045] (II) vmware: driver for VMware SVGA: vmware0405, vmware0710
[ 1431.045] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 1431.045] (II) FBDEV: driver for framebuffer: fbdev
[ 1431.045] (II) VESA: driver for VESA chipsets: vesa
[ 1431.045] (++) using VT number 1
[ 1431.045] (--) controlling tty is VT number 1, auto-enabling KeepTty
[ 1431.045] (WW) Falling back to old probe method for modesetting
[ 1431.045] (WW) Falling back to old probe method for fbdev
[ 1431.045] (II) Loading sub module "fbdevhw"
[ 1431.045] (II) LoadModule: "fbdevhw"
[ 1431.046] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[ 1431.046] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 1431.046] compiled for 1.16.2, module version = 0.0.2
[ 1431.046] ABI class: X.Org Video Driver, version 18.0
[ 1431.046] (WW) Falling back to old probe method for vesa
[ 1431.046] (II) vmware(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 1431.046] (--) vmware(0): DRM driver version is 2.6.1
[ 1431.046] (==) vmware(0): Depth 24, (--) framebuffer bpp 32
[ 1431.046] (==) vmware(0): RGB weight 888
[ 1431.046] (==) vmware(0): Default visual is TrueColor
[ 1431.046] (--) vmware(0): Min width 1, Max Width 8192.
[ 1431.046] (--) vmware(0): Min height 1, Max Height 8192.
[ 1431.047] (II) vmware(0): Output Virtual1 has no monitor section
[ 1431.047] (II) vmware(0): Output Virtual2 has no monitor section
[ 1431.047] (II) vmware(0): Output Virtual3 has no monitor section
[ 1431.048] (II) vmware(0): Output Virtual4 has no monitor section
[ 1431.048] (II) vmware(0): Output Virtual5 has no monitor section
[ 1431.048] (II) vmware(0): Output Virtual6 has no monitor section
[ 1431.048] (II) vmware(0): Output Virtual7 has no monitor section
[ 1431.048] (II) vmware(0): Output Virtual8 has no monitor section
[ 1431.048] (II) vmware(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 489 492 525 -hsync -vsync (31.5 kHz e)
[ 1431.048] (II) vmware(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 1431.048] (II) vmware(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 1431.048] (II) vmware(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
[ 1431.048] (II) vmware(0): Modeline "1280x768"x59.9 79.50 1280 1344 1472 1664 768 771 778 798 -hsync +vsync (47.8 kHz e)
[ 1431.048] (II) vmware(0): Modeline "1280x800"x59.8 83.50 1280 1352 1480 1680 800 803 809 831 +hsync -vsync (49.7 kHz e)
[ 1431.048] (II) vmware(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
[ 1431.049] (II) vmware(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[ 1431.049] (II) vmware(0): Modeline "1360x768"x60.0 85.50 1360 1424 1536 1792 768 771 777 795 +hsync +vsync (47.7 kHz e)
[ 1431.049] (II) vmware(0): Modeline "1400x1050"x60.0 121.75 1400 1488 1632 1864 1050 1053 1057 1089 -hsync +vsync (65.3 kHz e)
[ 1431.049] (II) vmware(0): Modeline "1440x900"x59.9 106.50 1440 1520 1672 1904 900 903 909 934 -hsync +vsync (55.9 kHz e)
[ 1431.049] (II) vmware(0): Modeline "1600x1200"x60.0 162.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (75.0 kHz e)
[ 1431.049] (II) vmware(0): Modeline "1680x1050"x60.0 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync (65.3 kHz e)
[ 1431.049] (II) vmware(0): Modeline "1792x1344"x60.0 204.75 1792 1920 2120 2448 1344 1345 1348 1394 -hsync +vsync (83.6 kHz e)
[ 1431.049] (II) vmware(0): Modeline "1856x1392"x60.0 218.25 1856 1952 2176 2528 1392 1393 1396 1439 -hsync +vsync (86.3 kHz e)
[ 1431.049] (II) vmware(0): Modeline "1920x1200"x59.9 193.25 1920 2056 2256 2592 1200 1203 1209 1245 -hsync +vsync (74.6 kHz e)
[ 1431.049] (II) vmware(0): Modeline "1920x1440"x60.0 234.00 1920 2048 2256 2600 1440 1441 1444 1500 -hsync +vsync (90.0 kHz e)
[ 1431.049] (II) vmware(0): Modeline "2560x1600"x60.0 348.50 2560 2752 3032 3504 1600 1603 1609 1658 -hsync +vsync (99.5 kHz e)
[ 1431.049] (II) vmware(0): Modeline "800x600"x60.0 42.75 800 850 900 950 600 650 700 750 -hsync +vsync (45.0 kHz eP)
[ 1431.049] (II) vmware(0): Printing probed modes for output Virtual1
[ 1431.049] (II) vmware(0): Modeline "800x600"x60.0 42.75 800 850 900 950 600 650 700 750 -hsync +vsync (45.0 kHz eP)
[ 1431.049] (II) vmware(0): Modeline "2560x1600"x60.0 348.50 2560 2752 3032 3504 1600 1603 1609 1658 -hsync +vsync (99.5 kHz e)
[ 1431.049] (II) vmware(0): Modeline "1920x1440"x60.0 234.00 1920 2048 2256 2600 1440 1441 1444 1500 -hsync +vsync (90.0 kHz e)
[ 1431.049] (II) vmware(0): Modeline "1856x1392"x60.0 218.25 1856 1952 2176 2528 1392 1393 1396 1439 -hsync +vsync (86.3 kHz e)
[ 1431.049] (II) vmware(0): Modeline "1792x1344"x60.0 204.75 1792 1920 2120 2448 1344 1345 1348 1394 -hsync +vsync (83.6 kHz e)
[ 1431.049] (II) vmware(0): Modeline "1920x1200"x59.9 193.25 1920 2056 2256 2592 1200 1203 1209 1245 -hsync +vsync (74.6 kHz e)
[ 1431.049] (II) vmware(0): Modeline "1600x1200"x60.0 162.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (75.0 kHz e)
[ 1431.049] (II) vmware(0): Modeline "1680x1050"x60.0 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync (65.3 kHz e)
[ 1431.049] (II) vmware(0): Modeline "1400x1050"x60.0 121.75 1400 1488 1632 1864 1050 1053 1057 1089 -hsync +vsync (65.3 kHz e)
[ 1431.049] (II) vmware(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[ 1431.049] (II) vmware(0): Modeline "1440x900"x59.9 106.50 1440 1520 1672 1904 900 903 909 934 -hsync +vsync (55.9 kHz e)
[ 1431.049] (II) vmware(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
[ 1431.049] (II) vmware(0): Modeline "1360x768"x60.0 85.50 1360 1424 1536 1792 768 771 777 795 +hsync +vsync (47.7 kHz e)
[ 1431.049] (II) vmware(0): Modeline "1280x800"x59.8 83.50 1280 1352 1480 1680 800 803 809 831 +hsync -vsync (49.7 kHz e)
[ 1431.049] (II) vmware(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
[ 1431.049] (II) vmware(0): Modeline "1280x768"x59.9 79.50 1280 1344 1472 1664 768 771 778 798 -hsync +vsync (47.8 kHz e)
[ 1431.049] (II) vmware(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 1431.049] (II) vmware(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 1431.049] (II) vmware(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 489 492 525 -hsync -vsync (31.5 kHz e)
[ 1431.049] (II) vmware(0): EDID for output Virtual2
[ 1431.049] (II) vmware(0): EDID for output Virtual3
[ 1431.049] (II) vmware(0): EDID for output Virtual4
[ 1431.049] (II) vmware(0): EDID for output Virtual5
[ 1431.049] (II) vmware(0): EDID for output Virtual6
[ 1431.049] (II) vmware(0): EDID for output Virtual7
[ 1431.049] (II) vmware(0): EDID for output Virtual8
[ 1431.049] (II) vmware(0): Output Virtual1 connected
[ 1431.049] (II) vmware(0): Output Virtual2 disconnected
[ 1431.049] (II) vmware(0): Output Virtual3 disconnected
[ 1431.049] (II) vmware(0): Output Virtual4 disconnected
[ 1431.049] (II) vmware(0): Output Virtual5 disconnected
[ 1431.049] (II) vmware(0): Output Virtual6 disconnected
[ 1431.049] (II) vmware(0): Output Virtual7 disconnected
[ 1431.049] (II) vmware(0): Output Virtual8 disconnected
[ 1431.049] (II) vmware(0): Using exact sizes for initial modes
[ 1431.049] (II) vmware(0): Output Virtual1 using initial mode 800x600
[ 1431.049] (II) vmware(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
[ 1431.049] (==) vmware(0): DPI set to (96, 96)
[ 1431.049] (II) Loading sub module "fb"
[ 1431.049] (II) LoadModule: "fb"
[ 1431.049] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 1431.050] (II) Module fb: vendor="X.Org Foundation"
[ 1431.050] compiled for 1.16.2, module version = 1.0.0
[ 1431.050] ABI class: X.Org ANSI C Emulation, version 0.4
[ 1431.050] (II) Loading sub module "dri2"
[ 1431.050] (II) LoadModule: "dri2"
[ 1431.050] (II) Module "dri2" already built-in
[ 1431.050] (II) UnloadModule: "modesetting"
[ 1431.050] (II) Unloading modesetting
[ 1431.050] (II) UnloadModule: "fbdev"
[ 1431.050] (II) Unloading fbdev
[ 1431.050] (II) UnloadSubModule: "fbdevhw"
[ 1431.050] (II) Unloading fbdevhw
[ 1431.050] (II) UnloadModule: "vesa"
[ 1431.050] (II) Unloading vesa
[ 1431.050] (==) Depth 24 pixmap format is 32 bpp
[ 1431.050] (II) vmware(0): Initialized VMWARE_CTRL extension version 0.2
[ 1431.064] (II) vmware(0): Gallium3D XA version: 2.2.0.
[ 1431.064] (II) vmware(0): Path of drm device is "/dev/dri/card0".
[ 1431.064] (II) vmware(0): [DRI2] Setup complete
[ 1431.064] (II) vmware(0): [DRI2] DRI driver: vmwgfx
[ 1431.064] (--) vmware(0): Render acceleration is enabled.
[ 1431.064] (==) vmware(0): Rendercheck mode is disabled.
[ 1431.064] (--) vmware(0): Direct rendering (3D) is enabled.
[ 1431.064] (==) vmware(0): Direct presents are disabled.
[ 1431.064] (==) vmware(0): Hardware only presents are disabled.
[ 1431.064] (==) vmware(0): Backing store enabled
[ 1431.064] (==) vmware(0): Silken mouse enabled
[ 1431.064] (II) vmware(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[ 1431.064] (==) vmware(0): DPMS enabled
[ 1431.064] (--) RandR disabled
[ 1431.075] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[ 1431.075] (II) AIGLX: enabled GLX_ARB_create_context
[ 1431.075] (II) AIGLX: enabled GLX_ARB_create_context_profile
[ 1431.075] (II) AIGLX: enabled GLX_EXT_create_context_es2_profile
[ 1431.075] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB
[ 1431.075] (II) AIGLX: enabled GLX_ARB_fbconfig_float
[ 1431.075] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
[ 1431.075] (II) AIGLX: Loaded and initialized vmwgfx
[ 1431.075] (II) GLX: Initialized DRI2 GL provider for screen 0
[ 1431.076] (EE)
Fatal server error:
[ 1431.076] (EE) failed to create screen resources(EE)
[ 1431.076] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 1431.076] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 1431.076] (EE)
[ 1431.076] (II) AIGLX: Suspending AIGLX clients for VT switch
[ 1431.076] (WW) vmware(0): drmDropMaster failed: Invalid argument
[ 1431.079] (EE) Server terminated with error (1). Closing log file.
Journal since boot
-- Logs begin at Wed 2014-11-19 16:23:50 CST, end at Fri 2014-11-21 14:25:54 CST. --
Nov 21 14:17:03 PingBuild kernel: pci_bus 0000:00: root bus resource [io 0x0d00-0xfeff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:00.0: [8086:7190] type 00 class 0x060000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:01.0: [8086:7191] type 01 class 0x060400
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:07.0: [8086:7110] type 00 class 0x060100
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:07.1: [8086:7111] type 00 class 0x01018a
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:07.1: reg 0x20: [io 0x10c0-0x10cf]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:07.1: legacy IDE quirk: reg 0x10: [io 0x01f0-0x01f7]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:07.1: legacy IDE quirk: reg 0x14: [io 0x03f6]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:07.1: legacy IDE quirk: reg 0x18: [io 0x0170-0x0177]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:07.1: legacy IDE quirk: reg 0x1c: [io 0x0376]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:07.3: [8086:7113] type 00 class 0x068000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:07.3: quirk: [io 0x1000-0x103f] claimed by PIIX4 ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:07.3: quirk: [io 0x1040-0x104f] claimed by PIIX4 SMB
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:07.7: [15ad:0740] type 00 class 0x088000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:07.7: reg 0x10: [io 0x1080-0x10bf]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:07.7: reg 0x14: [mem 0xd0000000-0xd0001fff 64bit]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:0f.0: [15ad:0405] type 00 class 0x030000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:0f.0: reg 0x10: [io 0x10d0-0x10df]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:0f.0: reg 0x14: [mem 0xd8000000-0xdbffffff pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:0f.0: reg 0x18: [mem 0xd0800000-0xd0ffffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:0f.0: reg 0x30: [mem 0x00000000-0x00007fff pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:10.0: [1000:0030] type 00 class 0x010000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:10.0: reg 0x10: [io 0x1400-0x14ff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:10.0: reg 0x14: [mem 0xd0040000-0xd005ffff 64bit]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:10.0: reg 0x1c: [mem 0xd0020000-0xd003ffff 64bit]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:10.0: reg 0x30: [mem 0x00000000-0x00003fff pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: [15ad:0790] type 01 class 0x060401
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: System wakeup disabled by ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.0: [15ad:07a0] type 01 class 0x060400
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.0: PME# supported from D0 D3hot D3cold
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.0: System wakeup disabled by ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.1: [15ad:07a0] type 01 class 0x060400
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.1: PME# supported from D0 D3hot D3cold
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.1: System wakeup disabled by ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.2: [15ad:07a0] type 01 class 0x060400
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.2: PME# supported from D0 D3hot D3cold
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.2: System wakeup disabled by ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: [15ad:07a0] type 01 class 0x060400
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: PME# supported from D0 D3hot D3cold
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: System wakeup disabled by ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: [15ad:07a0] type 01 class 0x060400
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: PME# supported from D0 D3hot D3cold
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: System wakeup disabled by ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: [15ad:07a0] type 01 class 0x060400
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: PME# supported from D0 D3hot D3cold
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: System wakeup disabled by ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: [15ad:07a0] type 01 class 0x060400
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: PME# supported from D0 D3hot D3cold
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: System wakeup disabled by ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: [15ad:07a0] type 01 class 0x060400
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: PME# supported from D0 D3hot D3cold
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: System wakeup disabled by ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.0: [15ad:07a0] type 01 class 0x060400
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.0: PME# supported from D0 D3hot D3cold
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.0: System wakeup disabled by ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.1: [15ad:07a0] type 01 class 0x060400
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.1: PME# supported from D0 D3hot D3cold
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.1: System wakeup disabled by ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.2: [15ad:07a0] type 01 class 0x060400
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.2: PME# supported from D0 D3hot D3cold
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.2: System wakeup disabled by ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: [15ad:07a0] type 01 class 0x060400
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: PME# supported from D0 D3hot D3cold
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: System wakeup disabled by ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: [15ad:07a0] type 01 class 0x060400
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: PME# supported from D0 D3hot D3cold
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: System wakeup disabled by ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: [15ad:07a0] type 01 class 0x060400
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: PME# supported from D0 D3hot D3cold
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: System wakeup disabled by ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: [15ad:07a0] type 01 class 0x060400
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: PME# supported from D0 D3hot D3cold
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: System wakeup disabled by ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: [15ad:07a0] type 01 class 0x060400
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: PME# supported from D0 D3hot D3cold
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: System wakeup disabled by ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.0: [15ad:07a0] type 01 class 0x060400
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.0: PME# supported from D0 D3hot D3cold
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.0: System wakeup disabled by ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.1: [15ad:07a0] type 01 class 0x060400
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.1: PME# supported from D0 D3hot D3cold
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.1: System wakeup disabled by ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.2: [15ad:07a0] type 01 class 0x060400
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.2: PME# supported from D0 D3hot D3cold
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.2: System wakeup disabled by ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: [15ad:07a0] type 01 class 0x060400
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: PME# supported from D0 D3hot D3cold
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: System wakeup disabled by ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: [15ad:07a0] type 01 class 0x060400
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: PME# supported from D0 D3hot D3cold
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: System wakeup disabled by ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: [15ad:07a0] type 01 class 0x060400
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: PME# supported from D0 D3hot D3cold
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: System wakeup disabled by ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: [15ad:07a0] type 01 class 0x060400
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: PME# supported from D0 D3hot D3cold
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: System wakeup disabled by ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.7: [15ad:07a0] type 01 class 0x060400
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.7: PME# supported from D0 D3hot D3cold
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.7: System wakeup disabled by ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.0: [15ad:07a0] type 01 class 0x060400
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.0: PME# supported from D0 D3hot D3cold
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.0: System wakeup disabled by ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.1: [15ad:07a0] type 01 class 0x060400
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.1: PME# supported from D0 D3hot D3cold
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.1: System wakeup disabled by ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: [15ad:07a0] type 01 class 0x060400
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: PME# supported from D0 D3hot D3cold
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: System wakeup disabled by ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.3: [15ad:07a0] type 01 class 0x060400
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.3: PME# supported from D0 D3hot D3cold
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.3: System wakeup disabled by ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.4: [15ad:07a0] type 01 class 0x060400
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.4: PME# supported from D0 D3hot D3cold
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.4: System wakeup disabled by ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.5: [15ad:07a0] type 01 class 0x060400
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.5: PME# supported from D0 D3hot D3cold
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.5: System wakeup disabled by ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.6: [15ad:07a0] type 01 class 0x060400
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.6: PME# supported from D0 D3hot D3cold
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.6: System wakeup disabled by ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.7: [15ad:07a0] type 01 class 0x060400
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.7: PME# supported from D0 D3hot D3cold
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.7: System wakeup disabled by ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:01.0: PCI bridge to [bus 01]
Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [32] registered
Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [33] registered
Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [34] registered
Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [35] registered
Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [36] registered
Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [37] registered
Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [38] registered
Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [39] registered
Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [40] registered
Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [41] registered
Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [42] registered
Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [43] registered
Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [44] registered
Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [45] registered
Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [46] registered
Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [47] registered
Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [48] registered
Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [49] registered
Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [50] registered
Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [51] registered
Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [52] registered
Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [53] registered
Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [54] registered
Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [55] registered
Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [56] registered
Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [57] registered
Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [58] registered
Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [59] registered
Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [60] registered
Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [61] registered
Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [62] registered
Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [63] registered
Nov 21 14:17:03 PingBuild kernel: pci 0000:02:00.0: [8086:100f] type 00 class 0x020000
Nov 21 14:17:03 PingBuild kernel: pci 0000:02:00.0: reg 0x10: [mem 0xd1020000-0xd103ffff 64bit]
Nov 21 14:17:03 PingBuild kernel: pci 0000:02:00.0: reg 0x18: [mem 0xd1000000-0xd100ffff 64bit]
Nov 21 14:17:03 PingBuild kernel: pci 0000:02:00.0: reg 0x20: [io 0x2000-0x203f]
Nov 21 14:17:03 PingBuild kernel: pci 0000:02:00.0: reg 0x30: [mem 0x00000000-0x0000ffff pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:02:00.0: PME# supported from D0 D3hot D3cold
Nov 21 14:17:03 PingBuild kernel: pci 0000:02:00.0: System wakeup disabled by ACPI
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: PCI bridge to [bus 02] (subtractive decode)
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [io 0x2000-0x3fff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [mem 0xd1000000-0xd23fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [mem 0xdc400000-0xdc9fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [mem 0x000a0000-0x000bffff] (subtractive decode)
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [mem 0x000cc000-0x000cffff] (subtractive decode)
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [mem 0x000d0000-0x000d3fff] (subtractive decode)
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [mem 0x000d4000-0x000d7fff] (subtractive decode)
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [mem 0x000d8000-0x000dbfff] (subtractive decode)
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [mem 0xc0000000-0xfebfffff] (subtractive decode)
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [io 0x0000-0x0cf7] (subtractive decode)
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [io 0x0d00-0xfeff] (subtractive decode)
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.0: PCI bridge to [bus 03]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.0: bridge window [io 0x4000-0x4fff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.0: bridge window [mem 0xd2400000-0xd24fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.0: bridge window [mem 0xd4400000-0xd44fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.1: PCI bridge to [bus 04]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.1: bridge window [io 0x8000-0x8fff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.1: bridge window [mem 0xd2800000-0xd28fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.1: bridge window [mem 0xd4800000-0xd48fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.2: PCI bridge to [bus 05]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.2: bridge window [io 0xc000-0xcfff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.2: bridge window [mem 0xd2c00000-0xd2cfffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.2: bridge window [mem 0xdcb00000-0xdcbfffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: PCI bridge to [bus 06]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: bridge window [mem 0xd3000000-0xd30fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: bridge window [mem 0xdcd00000-0xdcdfffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: PCI bridge to [bus 07]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: bridge window [mem 0xd3400000-0xd34fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: bridge window [mem 0xdcf00000-0xdcffffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: PCI bridge to [bus 08]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: bridge window [mem 0xd3800000-0xd38fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: bridge window [mem 0xdd100000-0xdd1fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: PCI bridge to [bus 09]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: bridge window [mem 0xd3c00000-0xd3cfffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: bridge window [mem 0xdd300000-0xdd3fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: PCI bridge to [bus 0a]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: bridge window [mem 0xd4000000-0xd40fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: bridge window [mem 0xdd500000-0xdd5fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.0: PCI bridge to [bus 0b]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.0: bridge window [io 0x5000-0x5fff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.0: bridge window [mem 0xd2500000-0xd25fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.0: bridge window [mem 0xd4500000-0xd45fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.1: PCI bridge to [bus 0c]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.1: bridge window [io 0x9000-0x9fff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.1: bridge window [mem 0xd2900000-0xd29fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.1: bridge window [mem 0xd4900000-0xd49fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.2: PCI bridge to [bus 0d]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.2: bridge window [io 0xd000-0xdfff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.2: bridge window [mem 0xd2d00000-0xd2dfffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.2: bridge window [mem 0xd4b00000-0xd4bfffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: PCI bridge to [bus 0e]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: bridge window [mem 0xd3100000-0xd31fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: bridge window [mem 0xd4d00000-0xd4dfffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: PCI bridge to [bus 0f]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: bridge window [mem 0xd3500000-0xd35fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: bridge window [mem 0xd4f00000-0xd4ffffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: PCI bridge to [bus 10]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: bridge window [mem 0xd3900000-0xd39fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: bridge window [mem 0xd5100000-0xd51fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: PCI bridge to [bus 11]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: bridge window [mem 0xd3d00000-0xd3dfffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: bridge window [mem 0xd5300000-0xd53fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: PCI bridge to [bus 12]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: bridge window [mem 0xd4100000-0xd41fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: bridge window [mem 0xd5500000-0xd55fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.0: PCI bridge to [bus 13]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.0: bridge window [io 0x6000-0x6fff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.0: bridge window [mem 0xd2600000-0xd26fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.0: bridge window [mem 0xd4600000-0xd46fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.1: PCI bridge to [bus 14]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.1: bridge window [io 0xa000-0xafff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.1: bridge window [mem 0xd2a00000-0xd2afffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.1: bridge window [mem 0xdca00000-0xdcafffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.2: PCI bridge to [bus 15]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.2: bridge window [io 0xe000-0xefff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.2: bridge window [mem 0xd2e00000-0xd2efffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.2: bridge window [mem 0xdcc00000-0xdccfffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: PCI bridge to [bus 16]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: bridge window [mem 0xd3200000-0xd32fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: bridge window [mem 0xdce00000-0xdcefffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: PCI bridge to [bus 17]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: bridge window [mem 0xd3600000-0xd36fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: bridge window [mem 0xdd000000-0xdd0fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: PCI bridge to [bus 18]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: bridge window [mem 0xd3a00000-0xd3afffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: bridge window [mem 0xdd200000-0xdd2fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: PCI bridge to [bus 19]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: bridge window [mem 0xd3e00000-0xd3efffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: bridge window [mem 0xdd400000-0xdd4fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.7: PCI bridge to [bus 1a]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.7: bridge window [mem 0xd4200000-0xd42fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.7: bridge window [mem 0xdd600000-0xdd6fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.0: PCI bridge to [bus 1b]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.0: bridge window [io 0x7000-0x7fff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.0: bridge window [mem 0xd2700000-0xd27fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.0: bridge window [mem 0xd4700000-0xd47fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.1: PCI bridge to [bus 1c]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.1: bridge window [io 0xb000-0xbfff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.1: bridge window [mem 0xd2b00000-0xd2bfffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.1: bridge window [mem 0xd4a00000-0xd4afffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: PCI bridge to [bus 1d]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: bridge window [io 0xf000-0xffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: bridge window [mem 0xd2f00000-0xd2ffffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: bridge window [mem 0xd4c00000-0xd4cfffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.3: PCI bridge to [bus 1e]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.3: bridge window [mem 0xd3300000-0xd33fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.3: bridge window [mem 0xd4e00000-0xd4efffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.4: PCI bridge to [bus 1f]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.4: bridge window [mem 0xd3700000-0xd37fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.4: bridge window [mem 0xd5000000-0xd50fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.5: PCI bridge to [bus 20]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.5: bridge window [mem 0xd3b00000-0xd3bfffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.5: bridge window [mem 0xd5200000-0xd52fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.6: PCI bridge to [bus 21]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.6: bridge window [mem 0xd3f00000-0xd3ffffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.6: bridge window [mem 0xd5400000-0xd54fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.7: PCI bridge to [bus 22]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.7: bridge window [mem 0xd4300000-0xd43fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.7: bridge window [mem 0xd5600000-0xd56fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 *9 10 11 14 15)
Nov 21 14:17:03 PingBuild kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 10 *11 14 15)
Nov 21 14:17:03 PingBuild kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 9 *10 11 14 15)
Nov 21 14:17:03 PingBuild kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 10 11 14 15) *0, disabled.
Nov 21 14:17:03 PingBuild kernel: ACPI: Enabled 2 GPEs in block 00 to 0F
Nov 21 14:17:03 PingBuild kernel: vgaarb: setting as boot device: PCI:0000:00:0f.0
Nov 21 14:17:03 PingBuild kernel: vgaarb: device added: PCI:0000:00:0f.0,decodes=io+mem,owns=io+mem,locks=none
Nov 21 14:17:03 PingBuild kernel: vgaarb: loaded
Nov 21 14:17:03 PingBuild kernel: vgaarb: bridge control possible 0000:00:0f.0
Nov 21 14:17:03 PingBuild kernel: PCI: Using ACPI for IRQ routing
Nov 21 14:17:03 PingBuild kernel: PCI: pci_cache_line_size set to 64 bytes
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: can't claim BAR 13 [io 0xf000-0xffff]: no compatible bridge window
Nov 21 14:17:03 PingBuild kernel: e820: reserve RAM buffer [mem 0x0009f800-0x0009ffff]
Nov 21 14:17:03 PingBuild kernel: e820: reserve RAM buffer [mem 0xbfef0000-0xbfffffff]
Nov 21 14:17:03 PingBuild kernel: NetLabel: Initializing
Nov 21 14:17:03 PingBuild kernel: NetLabel: domain hash size = 128
Nov 21 14:17:03 PingBuild kernel: NetLabel: protocols = UNLABELED CIPSOv4
Nov 21 14:17:03 PingBuild kernel: NetLabel: unlabeled traffic allowed by default
Nov 21 14:17:03 PingBuild kernel: HPET: 16 timers in total, 0 timers will be used for per-cpu timer
Nov 21 14:17:03 PingBuild kernel: hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
Nov 21 14:17:03 PingBuild kernel: hpet0: 16 comparators, 64-bit 14.318180 MHz counter
Nov 21 14:17:03 PingBuild kernel: Switched to clocksource hpet
Nov 21 14:17:03 PingBuild kernel: pnp: PnP ACPI init
Nov 21 14:17:03 PingBuild kernel: system 00:00: [io 0x1000-0x103f] could not be reserved
Nov 21 14:17:03 PingBuild kernel: system 00:00: [io 0x1040-0x104f] has been reserved
Nov 21 14:17:03 PingBuild kernel: system 00:00: [io 0x0cf0-0x0cf1] has been reserved
Nov 21 14:17:03 PingBuild kernel: system 00:00: Plug and Play ACPI device, IDs PNP0c02 (active)
Nov 21 14:17:03 PingBuild kernel: pnp 00:01: Plug and Play ACPI device, IDs PNP0b00 (active)
Nov 21 14:17:03 PingBuild kernel: pnp 00:02: Plug and Play ACPI device, IDs PNP0303 (active)
Nov 21 14:17:03 PingBuild kernel: pnp 00:03: Plug and Play ACPI device, IDs PNP0f13 (active)
Nov 21 14:17:03 PingBuild kernel: system 00:04: [mem 0xfed00000-0xfed003ff] has been reserved
Nov 21 14:17:03 PingBuild kernel: system 00:04: Plug and Play ACPI device, IDs PNP0103 PNP0c01 (active)
Nov 21 14:17:03 PingBuild kernel: pnp 00:05: Plug and Play ACPI device, IDs PNP0400 (active)
Nov 21 14:17:03 PingBuild kernel: pnp 00:06: Plug and Play ACPI device, IDs PNP0501 (active)
Nov 21 14:17:03 PingBuild kernel: pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Nov 21 14:17:03 PingBuild kernel: pnp 00:08: [dma 2]
Nov 21 14:17:03 PingBuild kernel: pnp 00:08: Plug and Play ACPI device, IDs PNP0700 (active)
Nov 21 14:17:03 PingBuild kernel: system 00:09: [io 0x1060-0x107f] has been reserved
Nov 21 14:17:03 PingBuild kernel: system 00:09: [mem 0xe0000000-0xefffffff] has been reserved
Nov 21 14:17:03 PingBuild kernel: system 00:09: [mem 0xd0200000-0xd03fffff] has been reserved
Nov 21 14:17:03 PingBuild kernel: system 00:09: Plug and Play ACPI device, IDs PNP0c02 (active)
Nov 21 14:17:03 PingBuild kernel: pnp: PnP ACPI: found 10 devices
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: bridge window [io 0x1000-0x0fff] to [bus 06] add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: bridge window [io 0x1000-0x0fff] to [bus 07] add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: bridge window [io 0x1000-0x0fff] to [bus 08] add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: bridge window [io 0x1000-0x0fff] to [bus 09] add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: bridge window [io 0x1000-0x0fff] to [bus 0a] add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: bridge window [io 0x1000-0x0fff] to [bus 0e] add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: bridge window [io 0x1000-0x0fff] to [bus 0f] add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: bridge window [io 0x1000-0x0fff] to [bus 10] add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: bridge window [io 0x1000-0x0fff] to [bus 11] add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: bridge window [io 0x1000-0x0fff] to [bus 12] add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: bridge window [io 0x1000-0x0fff] to [bus 16] add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: bridge window [io 0x1000-0x0fff] to [bus 17] add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: bridge window [io 0x1000-0x0fff] to [bus 18] add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: bridge window [io 0x1000-0x0fff] to [bus 19] add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.7: bridge window [io 0x1000-0x0fff] to [bus 1a] add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: bridge window [io 0x1000-0x0fff] to [bus 1d] add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.3: bridge window [io 0x1000-0x0fff] to [bus 1e] add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.4: bridge window [io 0x1000-0x0fff] to [bus 1f] add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.5: bridge window [io 0x1000-0x0fff] to [bus 20] add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.6: bridge window [io 0x1000-0x0fff] to [bus 21] add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.7: bridge window [io 0x1000-0x0fff] to [bus 22] add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.7: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.3: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.4: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.5: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.6: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.7: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:0f.0: BAR 6: assigned [mem 0xc0000000-0xc0007fff pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:10.0: BAR 6: assigned [mem 0xc0008000-0xc000bfff pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.7: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.7: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.3: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.3: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.4: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.4: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.5: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.5: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.6: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.6: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.7: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.7: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.7: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.7: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.6: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.6: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.5: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.5: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.4: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.4: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.3: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.3: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.7: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.7: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: BAR 13: no space for [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: BAR 13: failed to assign [io size 0x1000]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:01.0: PCI bridge to [bus 01]
Nov 21 14:17:03 PingBuild kernel: pci 0000:02:00.0: BAR 6: assigned [mem 0xd1010000-0xd101ffff pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: PCI bridge to [bus 02]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [io 0x2000-0x3fff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [mem 0xd1000000-0xd23fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [mem 0xdc400000-0xdc9fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.0: PCI bridge to [bus 03]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.0: bridge window [io 0x4000-0x4fff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.0: bridge window [mem 0xd2400000-0xd24fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.0: bridge window [mem 0xd4400000-0xd44fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.1: PCI bridge to [bus 04]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.1: bridge window [io 0x8000-0x8fff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.1: bridge window [mem 0xd2800000-0xd28fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.1: bridge window [mem 0xd4800000-0xd48fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.2: PCI bridge to [bus 05]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.2: bridge window [io 0xc000-0xcfff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.2: bridge window [mem 0xd2c00000-0xd2cfffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.2: bridge window [mem 0xdcb00000-0xdcbfffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: PCI bridge to [bus 06]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: bridge window [mem 0xd3000000-0xd30fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: bridge window [mem 0xdcd00000-0xdcdfffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: PCI bridge to [bus 07]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: bridge window [mem 0xd3400000-0xd34fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: bridge window [mem 0xdcf00000-0xdcffffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: PCI bridge to [bus 08]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: bridge window [mem 0xd3800000-0xd38fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: bridge window [mem 0xdd100000-0xdd1fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: PCI bridge to [bus 09]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: bridge window [mem 0xd3c00000-0xd3cfffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: bridge window [mem 0xdd300000-0xdd3fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: PCI bridge to [bus 0a]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: bridge window [mem 0xd4000000-0xd40fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: bridge window [mem 0xdd500000-0xdd5fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.0: PCI bridge to [bus 0b]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.0: bridge window [io 0x5000-0x5fff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.0: bridge window [mem 0xd2500000-0xd25fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.0: bridge window [mem 0xd4500000-0xd45fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.1: PCI bridge to [bus 0c]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.1: bridge window [io 0x9000-0x9fff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.1: bridge window [mem 0xd2900000-0xd29fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.1: bridge window [mem 0xd4900000-0xd49fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.2: PCI bridge to [bus 0d]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.2: bridge window [io 0xd000-0xdfff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.2: bridge window [mem 0xd2d00000-0xd2dfffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.2: bridge window [mem 0xd4b00000-0xd4bfffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: PCI bridge to [bus 0e]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: bridge window [mem 0xd3100000-0xd31fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: bridge window [mem 0xd4d00000-0xd4dfffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: PCI bridge to [bus 0f]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: bridge window [mem 0xd3500000-0xd35fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: bridge window [mem 0xd4f00000-0xd4ffffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: PCI bridge to [bus 10]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: bridge window [mem 0xd3900000-0xd39fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: bridge window [mem 0xd5100000-0xd51fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: PCI bridge to [bus 11]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: bridge window [mem 0xd3d00000-0xd3dfffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: bridge window [mem 0xd5300000-0xd53fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: PCI bridge to [bus 12]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: bridge window [mem 0xd4100000-0xd41fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: bridge window [mem 0xd5500000-0xd55fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.0: PCI bridge to [bus 13]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.0: bridge window [io 0x6000-0x6fff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.0: bridge window [mem 0xd2600000-0xd26fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.0: bridge window [mem 0xd4600000-0xd46fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.1: PCI bridge to [bus 14]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.1: bridge window [io 0xa000-0xafff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.1: bridge window [mem 0xd2a00000-0xd2afffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.1: bridge window [mem 0xdca00000-0xdcafffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.2: PCI bridge to [bus 15]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.2: bridge window [io 0xe000-0xefff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.2: bridge window [mem 0xd2e00000-0xd2efffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.2: bridge window [mem 0xdcc00000-0xdccfffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: PCI bridge to [bus 16]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: bridge window [mem 0xd3200000-0xd32fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: bridge window [mem 0xdce00000-0xdcefffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: PCI bridge to [bus 17]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: bridge window [mem 0xd3600000-0xd36fffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: bridge window [mem 0xdd000000-0xdd0fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: PCI bridge to [bus 18]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: bridge window [mem 0xd3a00000-0xd3afffff]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: bridge window [mem 0xdd200000-0xdd2fffff 64bit pref]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: PCI bridge to [bus 19]
Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: briTrilby wrote:
Thanks, that all sounds correct to me, unfortunalte I can't provide more help as I've never used vmware. But a couple pointers for pacman use:
There is no need to use that pipe, `pacman -Q <searchterm>` will work.
The reason you don't see the mouse package is that grep is case sensitive. `pacman -Q | grep -i vmware` should also show the mouse package, but this would be much easier as `pacman -Qs vmware` which allows pacman to do the search. Pacman's search is case-insensitive by default and is a bit more effient that listing all packages and grepping through them.
Got it. Yes using the 'vmware' the vmmouse shows up. Also searching 'svga' shows Mesa DRI drivers. That is another advantage for letting pacman search, since my search term was svga and what was dispalayed did not have that in the string, pacman search can see behind the covers. :-)
All this learning is good, now if I could just figure out why 'startx' is failing to create screen resource. ;-)
Question, does it matter what tty it starts on? I am using 0 (obvious from the log name), could that be an issue? Just thinking out loud. -
****PLEASE HELP ME SOMEONE**** PLEASE - Re: ON SCREEN CAPS LOCK INDICATOR
can someone please help me before i pull all of my hair out.
i have windows vista - 64 bit - the HP IQ500 touchsmart with a wireless keyboard.
in the systray the num caps and scroll lock appears as little blue boxes (when on).
everynow and again they simply disapper.
i researced how to activate them again but cant remember how to do it.
there is a way without having to mess with the registry and without downloading any program
i just cant remember how. i know wherever it is...you ultimately get 3 boxes that you can check in order to turn the options back on.
i am not talking about toggling, or sound, or mscofig and then boot.
does anyone know the steps to turn the caps scroll and num lock indicator in teh sys tray back on
oh, and right clicking on the toolbar and going to the notificiation area is not what i am referring to either.
I checked in the control panel programs and the hp on screen caps lock indicator etc program is there.
I reinstalled it nonetheless and confirmed it is installed properly
When I right click on the notification area I do to properties/notification area/customize
There are two lists there
1. Current Items and
2. Past Items
For some reason I see caps lock - scroll lock and num lock under the past items
There you are also able to change the status of the items to either Hide wne active, hide or show
All three (caps/num/scroll) are SHOW
I click apply OK then apply
I restart the computer and nothing. The on screen caps lock indicator is still not in the notification area/systray area
I repeat teh steps to ensure that the three have the SHOW option chosen and they are.
So....
Program is installed
Items are check for SHOW
Restart was done
Ohhh and also...I went to MSCONFIG and made sure that the HP Keyboard Program was selected/check mark as one of the start up programs.
There in a run command to activiate the 3rd party program (hp onscreen indicator program)
When you enter the run command that I cant remember...you then get this option where there are three check boxes...one next to num lock - one next to caps lock and one for scroll lock.
Once you check/select the boxes/options you want...presto they appear in the sys tray/notification area.
I just cant remember the run command it to save my life.
Please....put my mind to ease...cause I am losing it!
I just cant seem to "walk away"...must be my OCD :-(
ThanksNO.
We are all iPhone users just like you.
Apple has no blacklist.
You can contact your carrier and see if they offer such a service.
You cannot block it at all.
Sorry -
Is there a way that I can use QTP to produce screen caps (jpg, png or whatever image format) of a .mov file? Every so many frames. Or is there another program that will do a better job of this?
Thanks for any helpThanks Colin, but under "Export Image Sequence Settings" I don't see "fractional frame rate" just "Frames per second". Where do I find that setting?
Actually, Tony was referring to how you enter the frame rate itself here. Instead of entering whole numbers (e.g., 1, 3, 5, 7, 9. etc.), enter a fractional number as in his example (e.g., 0.1, 0.5, 0.25, 0.01, etc.). Just tested it on a 139.87 sec files. It produced 14 stills in the format I selected.
Nice trick, Tony. Will have to remember this one. -
Wondering if anyone could help me out here. I have a 30 minute sequence, and I want to grab a ton of still screen caps to use as jpgs of the clip. Is there a way to do a kind of batch job where i specify to grab one frame every 5 seconds or every so many frames and turn them into jpgs?
I am using version 5 if that info is needed.There is no tool to automate this withing FCP. You'll want to export using Quicktime conversion > Still Image. This topic of exporting many still has been discussed many times so a search will probably yield answers.
-
How can I capture a specific number of screen caps
Using final cut or any other application, how can I capture a specific number of screen caps? Each video will have a different length.
Bob,
Please clarify your question. Are you asking about screen captures? If so, what software are you using and what does this have to do with FCP?
-DH -
I'm trying to make a stop motion educational white board video. We tried with the phone and iPad and there were too many shadows and bad lighting. So I wanted to try using the Wacom tablet (which I can trace drawings) and using screen caps. But of course I want the pictures to be full screen or I want a partial screen cap because I don't want to edit 1000 photos. I could use the iPad and the bamboo paper app- am I missing any other options or ways to make this easier?
Neale,
Thanks for that. I had never used Alt+Prt Scr on my Sager, and did not know of the specifics of that modifier key. On my laptop, I need to do Ctrl+Prt Scr, rather than the more common Prt Scr (no modifier key), but that is fairly specific to my Sager on the Clevo MoBo, with its keyboard. On many computers, just plain Prt Scr is all that's needed.
I'll experiment with Alt+Prt Scr, as that might actually save me a Crop in PS, when doing a screen-cap.
Thanks,
Hunt -
Does anyone know how to make screen caps? I can freeze frame using the DVD Player, but I can't select the image to make a screen cap.
Thanks!
Kittenmommy.Apple Shift 4
It will either put the captured shot on your Desktop
or your Mac HD.
It will place a bullseye on your screen. Move your
mouse to a starting position and single click and
hold and outline while you are holding the click down
and when you are finished dragging and release and
you will have a shot of the highlighted area.
I got a dialogue box saying "Screen grabs are unavailable during DVD playback. Please quit DVD Player and try again."
Is there some other software I can use to play DVDs and make a screen cap? Thanks,
Kittenmommy. -
How to create screen resolution in bdc table control
hi gurus
can anyone suggest me
how to create screen resolution in bdc table control
thanks®ards
mark.Hi ,
Using CTU_PARAMS table for screen resolution .
For this sample code.
This is for Transation FB60.
report ZZFB60
no standard page heading line-size 255.
tables t100.
PARAMETERS : p_file1 like rlgrap-filename,
p_doctyp like RF05A-BUSCS,
p_invdat like INVFO-BLDAT,
p_posdat like INVFO-BUDAT.
CONSTANTS : C_TRANS_FB60(4) VALUE 'FB60'.
*Parameter string for runtime of CALL TRANSACTION
data : l_option type ctu_params,
l_subrc type sysubrc.
DATA : l_mstring(150).
data accnt type char17.
data : day type char2,
month type char2,
year type char4,
date1 type char10,
date2 type char10.
data : cnt(2) TYPE n,
cnt1 type i,
fld(25) TYPE c.
data : begin of excel occurs 0,
fieldname(255) type c,
end of excel.
DATA:BEGIN OF it_mess OCCURS 0,
msgtyp(5),
lms(200),
msgv1(50),
END OF it_mess.
data: begin of t_record occurs 0,
BUKRS(004),
ACCNT(017),
XBLNR(016),
WRBTR1(016),
WAERS(005),
SECCO(004) ,
SGTXT(050),
HKONT(010),
WRBTR2(017),
MWSKZ(002),
GSBER(004),
KOSTL(010),
end of t_record.
*Internal Table for Header Data
DATA : BEGIN OF t_head OCCURS 0,
BUKRS(004), "Company Code
ACCNT(017), "Account or Vendor
XBLNR(016), "Reference
WRBTR1(017), "Amount in document currency
WAERS(005), "Currency
SECCO(004), "Section Code
SGTXT(050), "Text
END OF t_head.
*Internal table for Item Data
DATA : BEGIN OF t_item OCCURS 0,
ACCNT(017), "Account
HKONT(010), "GL Account
WRBTR2(017), "Line item Amount in document currency
MWSKZ(002), "Tax Code
GSBER(004), " Business Area
KOSTL(010), "Cost centre
END OF t_item.
DATA: IT_BDCDATA LIKE BDCDATA OCCURS 0 WITH HEADER LINE,
IT_BDC_MESSAGES LIKE BDCMSGCOLL OCCURS 0 WITH HEADER LINE.
*include bdcrecx1.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file1.
PERFORM file_selection.
PERFORM data_upload.
PERFORM table_control.
start-of-selection.
l_option-defsize = 'X'.
l_option-dismode = 'A'.
l_option-updmode = 'S'.
day = p_invdat+6(2).
month = p_invdat+4(2).
year = p_invdat+0(4).
concatenate day month year into date1 SEPARATED BY '.'.
day = p_posdat+6(2).
month = p_posdat+4(2).
year = p_posdat+0(4).
concatenate day month year into date2 SEPARATED BY '.'.
*perform open_group.
loop at t_head.
CLEAR IT_BDCDATA.
REFRESH IT_BDCDATA.
perform bdc_dynpro using 'SAPLACHD' '1000'.
perform bdc_field using 'BDC_OKCODE' '=ENTR'.
perform bdc_field using 'BKPF-BUKRS' t_head-bukrs.
perform bdc_dynpro using 'SAPMF05A' '1100'.
perform bdc_field using 'BDC_OKCODE' '/00'.
perform bdc_field using 'RF05A-BUSCS' p_doctyp.
perform bdc_field using 'INVFO-ACCNT' t_head-accnt.
perform bdc_field using 'INVFO-BLDAT' date1.
perform bdc_field using 'INVFO-BUDAT' date2.
perform bdc_field using 'INVFO-XBLNR' t_head-xblnr.
perform bdc_field using 'INVFO-WRBTR' t_head-wrbtr1.
perform bdc_field using 'INVFO-WAERS' t_head-waers.
perform bdc_field using 'INVFO-SECCO' t_head-secco.
perform bdc_field using 'INVFO-SGTXT' t_head-sgtxt.
cnt = 1.
cnt1 = 1.
loop at t_item where accnt = t_head-accnt.
*if cnt > 4.
*cnt = 4.
*endif.
if cnt1 gt 1.
CONCATENATE 'ACGL_ITEM-MARKSP(' cnt ')' INTO fld.
perform bdc_field using fld 'X'.
perform bdc_dynpro using 'SAPMF05A' '1100'.
perform bdc_field using 'BDC_OKCODE' '=0005'.
endif.
perform bdc_dynpro using 'SAPMF05A' '1100'.
perform bdc_field using 'BDC_OKCODE' '/00'.
CONCATENATE 'ACGL_ITEM-HKONT(' cnt ')' INTO fld.
perform bdc_field using fld t_item-hkont.
CONCATENATE 'ACGL_ITEM-WRBTR(' cnt ')' INTO fld.
perform bdc_field using fld t_item-wrbtr2.
CONCATENATE 'ACGL_ITEM-MWSKZ(' cnt ')' INTO fld.
perform bdc_field using fld t_item-mwskz.
CONCATENATE 'ACGL_ITEM-GSBER(' cnt ')' INTO fld.
perform bdc_field using fld t_item-gsber.
CONCATENATE 'ACGL_ITEM-KOSTL(' cnt ')' INTO fld.
perform bdc_field using fld t_item-kostl.
perform bdc_field using 'BDC_CURSOR' fld.
*CONCATENATE 'ACGL_ITEM-MARKSP(' cnt ')' INTO fld.
*perform bdc_field using fld 'X'.
cnt1 = cnt1 + 1.
*cnt = cnt + 1.
*if cnt > 1.
*perform bdc_dynpro using 'SAPMF05A' '1100'.
*perform bdc_field using 'BDC_OKCODE' '=0005'.
**perform bdc_field using 'BDC_OKCODE' '=0006'.
*endif.
endloop.
perform bdc_dynpro using 'SAPMF05A' '1100'.
perform bdc_field using 'BDC_OKCODE'
'=BS'.
perform bdc_dynpro using 'SAPMSSY0' '0120'.
perform bdc_field using 'BDC_OKCODE'
'=BU'.
*perform bdc_transaction using 'FB60'.
CALL TRANSACTION C_TRANS_FB60 USING IT_BDCDATA options from l_option
MESSAGES INTO IT_BDC_MESSAGES.
perform error.
perform errordownload.
endloop.
*perform close_group.
*Form data_upload
FORM data_upload .
CALL FUNCTION 'WS_UPLOAD'
EXPORTING
FILENAME = p_file1
FILETYPE = 'DAT'
TABLES
DATA_TAB = t_record.
ENDFORM. " data_upload
*Form file_selection
FORM file_selection .
CALL FUNCTION 'F4_FILENAME'
EXPORTING
program_name = syst-cprog
dynpro_number = syst-dynnr
field_name = 'p_file1'
IMPORTING
file_name = p_file1.
ENDFORM. " file_selection
Form BDC_DYNPRO
FORM BDC_DYNPRO using program dynpro.
CLEAR IT_BDCDATA.
IT_BDCDATA-PROGRAM = PROGRAM.
IT_BDCDATA-DYNPRO = DYNPRO.
IT_BDCDATA-DYNBEGIN = 'X'.
APPEND IT_BDCDATA.
endform.
*Form BDC_FIELD
FORM bdc_field using fnam fval.
CLEAR IT_BDCDATA.
IT_BDCDATA-FNAM = FNAM.
IT_BDCDATA-FVAL = FVAL.
APPEND IT_BDCDATA.
ENDFORM.
Table Control
FORM table_control .
LOOP AT t_record.
ON CHANGE OF t_record-accnt.
MOVE-CORRESPONDING t_record TO t_head.
APPEND t_head.
ENDON.
loop at t_head.
t_item-accnt = t_head-accnt.
t_item-hkont = t_record-hkont.
t_item-wrbtr2 = t_record-wrbtr2 .
t_item-mwskz = t_record-mwskz .
t_item-gsber = t_record-gsber .
t_item-kostl = t_record-kostl.
APPEND t_item.
endloop.
If t_record-level = 'H'.
t_head-bukrs = t_record-text1.
t_head-accnt = t_record-text2.
t_head-xblnr = t_record-text3.
t_head-wrbtr1 = t_record-text4.
t_head-waers = t_record-text5.
t_head-secco = t_record-text6.
t_head-sgtxt = t_record-text7.
APPEND t_head.
else.
t_item-accnt = t_head-accnt.
t_item-hkont = t_record-text1.
t_item-wrbtr2 = t_record-text2.
t_item-mwskz = t_record-text3.
t_item-gsber = t_record-text4.
t_item-kostl = t_record-text5.
APPEND t_item.
endif.
ENDLOOP.
ENDFORM.
FORM error .
LOOP AT IT_BDC_MESSAGES.
IF IT_BDC_MESSAGES-msgtyp = 'E'.
SELECT single * FROM t100 WHERE
sprsl = it_BDC_MESSAGES-msgspra
AND arbgb = IT_BDC_MESSAGES-msgid
AND msgnr = IT_BDC_MESSAGES-msgnr.
IF sy-subrc = 0.
l_mstring = t100-text.
IF l_mstring CS '&1'.
REPLACE '&1' WITH IT_BDC_MESSAGES-msgv1 INTO l_mstring.
REPLACE '&2' WITH IT_BDC_MESSAGES-msgv2 INTO l_mstring.
REPLACE '&3' WITH IT_BDC_MESSAGES-msgv3 INTO l_mstring.
REPLACE '&4' WITH IT_BDC_MESSAGES-msgv4 INTO l_mstring.
ELSE.
REPLACE '&' WITH IT_BDC_MESSAGES-msgv1 INTO l_mstring.
REPLACE '&' WITH IT_BDC_MESSAGES-msgv2 INTO l_mstring.
REPLACE '&' WITH IT_BDC_MESSAGES-msgv3 INTO l_mstring.
REPLACE '&' WITH IT_BDC_MESSAGES-msgv4 INTO l_mstring.
ENDIF.
CONDENSE l_mstring.
it_mess-msgtyp = IT_BDC_MESSAGES-msgtyp.
it_mess-lms = l_mstring.
it_mess-msgv1 = IT_BDC_MESSAGES-msgv1.
APPEND it_mess.
ELSE.
it_mess-msgtyp = IT_BDC_MESSAGES-msgtyp.
it_mess-lms = l_mstring.
it_mess-msgv1 = IT_BDC_MESSAGES-msgv1.
APPEND it_mess.
ENDIF.
ENDIF.
ENDLOOP.
ENDFORM.
form errordownload.
*down the internal table to excel file.
call function 'EXCEL_OLE_STANDARD_DAT'
EXPORTING
file_name = 'c:/Error.xls'
TABLES
data_tab = it_mess
fieldnames = excel
EXCEPTIONS
file_not_exist = 1
filename_expected = 2
communication_error = 3
ole_object_method_error = 4
ole_object_property_error = 5
invalid_filename = 6
invalid_pivot_fields = 7
download_problem = 8
others = 9.
endform.
Reward if useful
Regards,
Narasimha
Edited by: narasimha marella on May 13, 2008 12:12 PM -
Cannot select the newly created Screen variant in ENJOY transactions.
Hello All,
I have created a screen variant for a specific requirement from the client in transaction SHD0.
However I am unable to select this new screen variant in all ENJOY transactions.
When I try to select the screen variant in FB50-Post GL through>EDIT>Screen Variant, Select,Reset and Create Screen variants are greyyed out.
I have checked the setting in SU3, as well as FB00 for the Parameters, it appears to be correct.
Kindly help at the earliest!!
Regards
ShrutikaHi,
Shrutika.
Try this I hope this may help you.
Go to FB50 at above left hand side will see Tree On option button. Click on that you will see Screen vairants for items option with drop down object. Simply click on that now select your desired screen variant by double clicking applied.
I hope this may help you to solve your issue. If you have any doubts feel free to ask.
Regards,
Pankaj A Bhalerao. -
We have a requirement to create a contract with reference to another contract.
But we have a custom tab in the contract create screen. This information is stored in a custom table. So when I want to create the contract with reference to another contract. I want the custom tab information also to be pulled.
Can this be done.
Regards,
Chandra KumarHi,
I tried in the follow way IN above mentioned exit
i had written follow code -
<b> IF ZDATA-RATE IS INITIAL.
IF sy-tcode EQ 'VA41'.
CALL SCREEN 8309.
ENDIF.
ENDIF.</b>
But it giving error message as
<b>Screen SAPMV45A 8309 must not be an include screen</b>.
My main idea is to when my zfield[REQUIRED]-RATE is balnk i want to make my cursor to go and sit in <b>ADDITIONAL DATAB</b> tab in that RATE field.
Can anybody give their sujjestions!
Thanks,
Prasad. -
How to create screen variant in search criteria in POWL.
Hi All,
i have requirement to create screen data variant in POWL.
am using standard POWL application and custom feeder class, in which i created my selection screen fields.
User wants to save data entered in selection screen fields in the form of variant. He would like to use the variant everytime he inputs data instead of manually filling all the selection screen fields.
Is it possible to give user an option of saving variants in POWL selection criteria.
Thanks,
Praveenhi,
To show a default sold-to-party in this field when the user creates a sales order (VA01) we can use a function exit .This function exit is located in enhancement no V45A0002 . Before we can choose the exit we have to create a project in CMOD after that enter V45A0002 in the enhancement field and click on the components . In the components you will see the exit EXIT_SAPMV45A_002 . This exit is used for our purpose.
Double clicking on this exit will takes us to function builder (SE37) . This function exit has one exporting parameters and two importing parameters, we are interested in exporting parameter which is E_KUNNR of type KNA1-KUNNR i.e if we move the desired customer name to this structure(E_KUNNR) it will be shown in the field as the default value when we create the sales order. This function also contains a customer include ZXVVA04 . This include will be used to write our custom code .
Double clicking on this include and it will prompt us that this include does not exists do you want to create this object ,select yes and the include will be created .In this include we can write our own code that will fill the field E_KUNNR.
e.g. E_KUNNR = 301.
Activate the include and Activate the project. Now when ever the SALES ORDER will be created , sold-to-party field will come up with a predefined customer .
regards
sadhu kishore -
Someone has a tutorial for creating screen exit?
I have a development and I do not know how to create screen exit.
Case Someone has a tutorial for creating screen exit please help me
Thank you
<b><i>Wagner Duarte
Consultant - SAP ABAP</i></b>hI
Screen Exit is nothing but enhancing the screen like creating some more fields, subscreen and so on.
1. Go to the screen>System>Status-->Program (Double
click this program. It will take you to the program.
2. Now, Goto-->Object Directory Entry.
3. Make a note the package name.
4. Now run the transactions SMOD, press F4 and enter the
above noted package, press enter.
5. It will display list of Exits.
6. Now go back to the initial screen SMOD.
7. Specify the exit name here and select the radio button
Components.
8. It will display four group boxes one for FM, second
for Fcodes, thrid for Screen areas and last for
includes.
9. Goto transaction CMOD, create a new project, and
click the button "Enhancement assignments" and
specify your enhancements that you got in SMOD.
10. Now bouble clikc the enhancement, it will take you to editor with some includes starting with Z, double clikc the include you want to edit and proceed.
Have a look at below link It will definately help you to undestand the same.
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
check these links.
http://help.sap.com/saphelp_46c/helpdata/en/c8/1975e643b111d1896f0000e8322d00/frameset.htm
http://www.allsaplinks.com/screen_exit.html
USER EXITS
https://forums.sdn.sap.com/click.jspa?searchID=672084&messageID=312792
https://forums.sdn.sap.com/click.jspa?searchID=672084&messageID=1320078
https://forums.sdn.sap.com/click.jspa?searchID=672084&messageID=2669896
How to implement screen exit for a SAP standard transaction
Introduction
SAP provides standard transactions to enter data into database. But a client may want to maintain some additional information in SAP other than what is provided.
To make provisions for this, additional screens have to be provided and additional fields must be added into appropriate database table.
To pave way for this, SAP has provided the option for screen exits. Usually, SAP provides the following:
An append structure in the database table with the new fields.
A subscreen area into the standard screen where the programmer can attach his subscreen of his own program with the new fields.
A function group under which the new subscreen has to be created with the new fields.
Function exits to synchronize the PBO and PAI of the standard SAP program with the PBO and PAI of the subscreen so that data can flow back and forth between the standard SAP program and the program written by the developer for the subscreen. These function modules also exist in the same function group under which the subscreen will have to be developed.
Finally, a linkage has to be done between the subscreen area of standard SAP screen with the custom subscreen constructed by the developer.
Typically, SAP provides an enhancement in which the developer can create an append structure, use the function exits to synchronize the PBO and PAI of the standard SAP program and the custom subscreen program, and make the necessary linking( as mentioned above in step 4. But, again, this is not a hard and fast rule. Linking in some case, is also done by configurations.) SAP also usually provides the name of the function group under which the subscreen has to be developed.
Necessary guidance about implementing a screen exit development is usually available in the Documentation section of the enhancement ( can be availed by transaction SMOD).
Pre-Requisites
The developer to work on screen exit should have essential knowledge on the following:
DDIC concepts, including the knowledge of append structure.
Concept of SAP Enhancements and implementing them using Projects.
Concept of function exits.
Knowledge on Module Pool including subscreens, Tabstrip controls etc.
Steps
Guidelines
So, a developer can follow the guidelines mentioned below to implement a screen exit to a standard SAP transaction, as and when required:
Find out the Required Enhancements
Go to SMOD. Press F4 in the Enhancement field. In the next popup window, click pushbutton SAP Applications. A list will appear that contains information on all the enhancements, categorized under functional areas. Developer must search for the enhancements relevant to his functional area of interest for e.g., Purchasing, Asset Accounting, etc.
Note down the enhancements. Then, come to the initial screen of SMOD and view the documentation of each enhancement to find out which one is required for your development.
Utilize the Enhancement in a Project
After you have found one, do as directed in the documentation. Generally, the steps are as follows:
Create a project using CMOD including your enhancement.
Create the append structure with new fields.
Go to the desired function group and create a subscreen with the new fields. Write PBO and PAI for the subscreen, if required.
Use the function exits in the enhancement to link the PBO and PAI of the subscreen with that of the main SAP program supporting the SAP transaction.
Maintain necessary linkage between the subscreen area of standard SAP program with the custom subscreen developed along with the custom program name. This can be done in the project (developed by CMOD including the enhancement) or outside as a part of configuration.
Activate the project.
Test to ensure that required functionality are met.
Case Study 1
Add three new custom fields for Asset master and maintain information for them
Requirement
Three fields in the legacy system have to be maintained in Asset master. These fields are:
Original Asset number 20 characters
Location 2 15 Characters.
Model no 20 characters
Location 2 should start with L.
Pre-Analysis
Finding out the Enhancement
As described above, the enhancement is determined. It was found, that enhancement AIST0002 will serve the purpose. It contains the following components (can be viewed by transaction SMOD):
Exit Type Description EXIT_SAPL1022_001 Function Exit Check of User-Defined Fields when Using Create and Change BAPI EXIT_SAPLAIST_002 Function Exit Transfer Data for User Subscreens in PBO. EXIT_SAPLAIST_003 Function Exit Transfer of User-Defined Fields to SAP Master Data Transactions CI_ANLU Customizing Include Include structure to add new fields
Studying the Function Exits
The function module level documentation for the function exits are then viewed from transaction SE37. The documentation clearly laid out for the purpose for their use:
EXIT_SAPLAIST_002
Function module Level Documentation
This function module is called by asset master data maintenance at the start of the dialog. (When changing, it is called after reading of the data from the database; when creating it is called after the transfer of the default values from the asset class and reference asset.) The purpose of the function module is to enable this function group to recognize the master data. For interpreting or controlling master data fields that are important for user fields, it is possible to transfer to global variables at this point, so that they can be recognized when the user subscreens are processed.
Import Parameters
Understanding
This function module is called at the PBO to pass the information retrieved from the database to pass them to the custom subscreen and its underlying program. Import parameter : I_ANLU will be populated with the values for user-defined fields which will be passed to the subscreen program. So, there must be some sort of variable assignment from I_ANLU.
EXIT_SAPLAIST_003
Function module Documentation: This function module is called by SAP asset master data maintenance after the screens are processed, but before saving. The purpose of the function module is to transfer fields entered on user sub-screens of SAP asset data maintenance to the database for updating. The export parameter for this function module is:
Understanding
This function module will be used to transfer the user entered data in the subscreen fields to the main SAP program, which will then be saved into the database.
Studying the Documentation of the Enhancement
The enhancement documentation (as is viewed from the initial screen of SMOD] also supports the idea. Moreover, it informs that we need to develop a subscreen under function group XAIS. This is the function group under which the two function exit modules also exist. So, if the custom subscreen refers to the global data of the function group XAIS, then those values will also be available to these function exits as well.
Going to SE80 and viewing the function group XAIS helps us to inform that there are three DDIC tables declared for it:
Deciding the Final course of Action
After making all the investigations, the final course of action was determined.
SrlNo Step Justification
A project has to be created using transaction CMOD where the enhancement AIST0002 will be included.
Customizing include CI_ANLU has to be created with the custom fields demanded When CI_ANLU will be developed, the custom fields will get appended to the database table ANLU. Also, these fields will be used to create screen fields in the new subscreen.
A custom subscreen, say, 9000 will be developed under function group XAIS. The screen group for the screen will be CUST (or any name). The three custom fields added to table ANLU (by creating CI_ANLU) will be used to create new fields in the screen.
In the PAI of the subscreen, validation for Location to start with L will be added. The subscreen with three new fields has to be developed so that it can be attached to a subscreen area of the asset master screens.
In the custom include of the function exit module EXIT_SAPLAIST_002, the following code will be written:-
ANLU = I_ANLU. I_ANLU is the import parameter of this FM. The value is assigned to the global variable ANLU, referring which the three new subscreen fields are developed. So, data retrieved from database table ANLU will be passed to this FM as I_ANLU by the standard SAP main program. The value will be taken and passed to the global variable of the function group XAIS, so that the three custom fields (referring to ANLU of XAIS) get populated.
In the custom include of the function exit module EXIT_SAPLAIST_003, the following code will be written:-
E_ANLU = ANLU. The changed values in the subscreen fields exist in global variable ANLU for the function group XAIS. This function exit module will pass the data back to the SAP main program as E_ANLU.
Proper linkage/configuration has to be done so that the new subscreens get linked to the appropriate subscreen area of the Asset master screen. This has to be done otherwise, the new custom subscreen will not be displayed in the Asset master screens.
Development
Creating a Project to include the enhancement
Go to transaction CMOD and create a project.
Enter a description for the project. Then, click on the pushbutton Enhancement Assignments in the Application Toolbar.
Enter the name of the enhancement and Save.
Go to Components.
Creating Custom Include for ANLU
The screen shown below will appear, showing all the enhancement components under the assignment AIST0002. Double-click on the name of the Include Structure to create it.
Create the include structure with three new fields, as required. Then, save and activate it.
Develop the subscreen and the program
Go to transaction SE80. For the function group XAIS, create a new subscreen 9000.
Create it as subscreen.
Then, go to the Layout of the screen and create three new fields from Database table ANLU.
Drag the fields in the screen body and place them.
Then, save and activate the screen and come back to screen flow editor.
Create the PAI module to add validation for field Location 2, as required .
Activate the whole function group and come out.
Write code in the Function Exits to synchronize the programs
Now, code has to be written in the function modules EXIT_SAPLAIST_002 and EXIT_SAPLAIST_003 so that data flows to and fro between the main SAP program and custom subscreen program. For that, go back to transaction CMOD and change the function exits.
Write code in the function module EXIT_SAPLAIST_002 called once at the beginning of the transaction:
Write code in EXIT_SAPLAIST_003 to pass the data from the subscreen to SAP main program.
Then, activate everything the whole project and come out.
Complete the configuration to link the subscreen
The development portion is complete. Now, linking of the subscreen has to be done with the subscreen area of the main program. In most of the cases, this linking can be done in the enhancement itself. But, here, requirement is a bit different. It is done by configuration using SPRO.
Assets are created under Asset class. And for each asset class, there is a layout assigned to it. For a layout, there are multiple tab pages assigned to it. And, for each tab page, there are multiple screen groups/field groups assigned.
Here, the requirement is to create these three custom fields in the tab page General of asset master screen ( AS01/AS02/AS03/AS91).
Determine the Layout
To achieve this, first of all, we need to find out which layout is assigned to asset class 1000.For that, go to transaction AOLK( information has to be obtained from functional consultant).Select the Asset Class 1000 and click on folder General Assignment of Layout.
Here, for Asset class 1000, for all the user groups, tab layout SAP is assigned. Since layout SAP cannot be changed, it has to be copied and manipulated to include our screen group. Later, the new layout has to be assigned over here.
Create new tab layout
Go to transaction AOLA. Copy the tab layout SAP to create another layout, say, YSUB.
System will copy all the settings and will inform you about that.
Select your newly created layout and double-click on the folder Tab page titles.
You want to put your custom fields in the tab page General. So, select this tab page entry and double-click on the folder "Position of Groups".
Here, all the field groups currently residing in the tab-page General are shown. Add an entry for your newly created fields.
Select the group box from the list. An entry will come with U padded with the custom subscreen prepared by you.
Then, save and come out.
Assign the new Layout to Asset Class
Now, go to tcode AOLK and assign tab layout YSUB for asset class 1000.
Save and come out.
Test the Exit
Everything is over. Now, go to transaction code AS01/02/03 or AS91 to deal with an asset of asset class 1000. You will see your new fields added to the screen. Add values to them save. Then, enter into the tcodes again to see whether the values entered by you are being displayed or not.
Original Source: ittoolbox.com
Screen Exit is nothing but enhancing the screen like creating some more fields, subscreen and so on.
1. Go to the screen>System>Status-->Program (Double
click this program. It will take you to the program.
2. Now, Goto-->Object Directory Entry.
3. Make a note the package name.
4. Now run the transactions SMOD, press F4 and enter the
above noted package, press enter.
5. It will display list of Exits.
6. Now go back to the initial screen SMOD.
7. Specify the exit name here and select the radio button
Components.
8. It will display four group boxes one for FM, second
for Fcodes, thrid for Screen areas and last for
includes.
9. Goto transaction CMOD, create a new project, and
click the button "Enhancement assignments" and
specify your enhancements that you got in SMOD.
10. Now bouble clikc the enhancement, it will take you to editor with some includes starting with Z, double clikc the include you want to edit and proceed.
and you just go through these links also
Screen exit
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
screen-exits
Check the following link.
https://www.sdn.sap.com/irj/sdn/advancedsearch?query=how%20to%20find%20screen%20exits&cat=sdn_all
Maybe you are looking for
-
How do I stop my iTunes from freezing?
Hey everyone...I own a Windows Vista and an iPod Classic 160 GB. Recently, my iPod started skipping songs or ending them early. I restored it twice and that did nothing. I also completely uninstalled iTunes and reinstalled it - that did nothing. The
-
Illustrator crashes every time I open a file from Bridge
Every time I open an AI file from Bridge, it crashes Illustrator. Bridge stays open though. Any idea why???
-
Cisco ISE sponsor Portal email notification of guest account
Is there anyway to not have the email button be displayed in the sponsor portal? We don't have email or SMS enabled and sponsor users are complaining that the button is there but doesn't work, it woul be really good if you could just remove it. I h
-
Dear All SAP Gurus I am executing T.Code J2I5-Excise register extraction.Following error is coming Customization for Company-Plant 9090-9191 missing in table Excise Indicator for Plant Message no. 8I303 Diagnosis The customization details have not be
-
Error Msg when connecting iPod
Ok so i just bought my iPod and I can't get it to connect to my PC the msg i get is "One of the USB devices attached to this computer has malfunctioned, and windows does not recognize it.". Faulty iPod? or something else i might be missing? I also ha