Feature: Expose FCSH capability in ASC2.0 compiler
How much work would it be to expose the FCSH (Flex Compiler Shell) capability in the ASC2.0 command-line compiler? Obviously the functionality exists because Flash Builder uses it for fast compile times, but it's not availble from the command-line (aka, there's not an fcsh executable in the ASC2.0 compiler).
Is there any chance of this happening?
Thanks,
-Jeff
FYI for anyone interested in this topic, I've hacked a soution - an fcsh implementation for the asc 2.0 compiler. See my blog for details:
http://jcward.com/FCSH+for+ASC+2.0+Compiler
Similar Messages
-
Ping tbd : "feature" related to FP.Open and compiled apps
tbd,
In another thread you stated:
To programmatically pop-up the FP of a VI, set its FP.Open property to True. This can be done anywhere in the application, as long as the VI's reference is available (sounds like an application for a Global ). There's a "feature" related to FP.Open and compiled apps - do you plan to compile this?
Would you (or anyone) care to elaborate on this subject a bit. I am doing just this sort of thing and am interested in all insights and caveats.
Thanks
LabVIEW 8.0.1; WinDoze XP
aut viam inveniam aut faciamHi BadToad,
If the compiler doesn't think an FP is needed, based on a VI's appearance properties, it will exclude the VI's FP during compile - and FP.Open won't work for the VI. The attached pic shows this compiler setting in 7.1 and 8.2. If the VI is top-level, or one of its appearance-properties indicate the FP is to be shown, these will default to UNselected for remove, otherwise you'll need to deselect these for Open FP to work.
Cheers!
BTW - great user-name.
Message Edited by tbd on 03-02-2008 03:26 PM
"Inside every large program is a small program struggling to get out." (attributed to Tony Hoare)
Attachments:
OpenFP.JPG 95 KB -
What's the best way to mix AIR 14 and the Flex 3.5 SDK and use new AIR features?
I am returning to development of a popular desktop AIR app, after about 4 years of no code changes. Both AIR and Flex have actively moved forward during my coding absence, and it is time to play catch up.
When last built, the app was using Flex 3.5 and AIR 2.6.
End Goal - I want my app to look good on high density displays
I'd like to keep Flex version at 3.5, but use the newer version of AIR, to render more clearly on high density displays (Retina on OSX and hiDPI on Win8).
The pixel doubling performed by the "compatibility" modes of OSX.Retina or Win8.hiDPI make my app look pretty gross, and the customer base is starting to complain.
While I may eventually switch over to the Apache Flex SDK to bring the application design into the current state, my customer base just doesn't care right now. They like the current app, but want it to work, out-of-the-box, on high density displays.
So I need to limit my scope to changing only the AIR SDK, not the Flex SDK at this time.
Step 1 - Overlaying AIR14 SDK on Flex 3.5
I followed the official generic overlay instructions here, and that worked well enough. I named my hybrid SDK folder "3.5.0.AIR14". I have been able to recompile, run, and verify my app using the hybrid SDK. (my app is compiled and packaged from an ant script, using the Antennae framework. I had already switch SDKs a number of times over the initial course of development, so pointing my project to a new SDK was pretty simple enough.
Step 2 - Updating the app.xml descriptor
This part was also easy. I used the templates\air\descriptor-template.xml as a starting point, customizing the name, app id, and folders. Now my app descriptor is correctly based on the <application xmlns="http://ns.adobe.com/air/application/14.0"> namespace.
Step 3 - Enabling Retina/hiDPI support - Help??
I added <requestedDisplayResolution>high</requestedDisplayResolution> to the <initialWindow> tag of the app descriptor, but that made no difference. The app compiles, installs, and runs, but pixel doubling is still occurring and the app looks gross.
I also tried setting the SWF version to 25, according to the official overlay guide. This proved to be more difficult. The official overlay guide suggests setting the -swf-version=25 compiler option, but that option is not supported by the Flex 3.5 compiler. So all I had to try was using the legacy -target-player=25 compiler option. That setting was accepted by the compiler, and it produced a SWF with byte offset 0x3 == 0x19 (25 dec), so that appears to be right.
But -target-player=25 didn't have any effect either.
Is setting the SWF version even required? Isn't the whole point of using the AIR 14 namespace in the app descriptor the way of telling the compiler "I want to use all features of the AIR 14 release". Why do I need to tell the compiler multiple times to use all the features of the SDK I'm compiling with? It just seems weird to me.
Have I missed a secret setting somewhere?
How can I tell the AIR runtime to simply run as pixel-dense as possible? When the workarounds listed below are performed, my app looks fantastic on high-density displays. But its the pixel scaling that is making everything look bad, and I desperately want to get this fixed.
Workarounds?
On Windows 8+, we are asking our users to enable the "Disable display scaling on high DPI settings" checkbox on the AIR application shortcut. This works, but is a confusing setting for average users to discover. Most just give up in frustration.
On OSX, we can't even disable Retina mode on a per-application basis, its all or nothing, so that's even worse. SwitchResX will automatically switch resolutions based on the selected app, but that's a pretty clunky (and non-free) workaround too.
Any other workaround ideas are appreciated too.
Cheers,
DougIt took me a while to figure out (without much help from Adobe, grrr!), since some internet writeups were terse and implied somehow that AIR's Retina support (setting your app descriptor's <initialWindow/requestedDisplayResolution> to high) would also work on Windows. They don't.
On OSX, the steps to disable pixel-doubling are:
update your app descriptor to AIR 14
set initialWindow/requestedDisplayResolution = high
compile with SWF version 25 or greater
vector assets, including text, will scale automatically
you'll need to replace your bitmap assets with Retina-quality bitmaps as appropriate
when running on a Retina display, you will see stage.contentsScaleFactor=2. It will be 1 for non-Retina displays.
On Windows, the pixel-doubling kicks in when you have a HiDPI scaling set to about 150% or greater (hiDPI scaling was introduced in Win7). There is no way to detect from within an AIR app when Windows is doing its HiDPI scaling. stage.contentsScaleFactor is always 1, under all configurations.
The only thing you can do for AIR apps on Windows is explicitly disable display scaling (like you have done) and update your app to manually scale all UI elements at runtime (that's really gross and hard, and it what I working on right now).
For my app, I updated our Windows installer to set the registry to disable hiDPI scaling, for all users, just for our app. Here's how you do that:
Key = HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers
Name = <fullPathToYourExe>
Type = REG_SZ
Value = "~ HIDPIAWARE" (without the quotes, tilde space HIDPIAWARE)
That should be set in the full 64-bit registry, not the Wow32Node registry, even if your app is a 32-bit app (which all AIR apps are). If your installer is a 32-bit app (mine was), you may need to jump through some hoops to have it affect the 64-bit registry hive from a 32-bit process.
If you only want to change the setting for the current user (not all users), the KEY root is HKEY_CURRENT_USER instead of HKEY_LOCAL_MACHINE.
If you don't have an explicit installer for your AIR app (ie. if you are deploying from the web via a badge installer), then you're even more messed up, and you will need to tell your users to disable the scaling manually.
I know, it's a total pain. I hope this helps.
Cheers,
Doug
PS: Adobe devs, if you are listening ... -
Ubuntu 15.04 guest shared folders feature not working
I've attempted to use the tools from the player, use the open-vm-tools package. I even tried compiling open-vm-tools from source and I could fix some compilation errors but it got too complicated. After spending half a day on it, I gave up.
Running the vmware-config-tools.pl script gives errors.
Some of the output of running the script is below.
The VMware Host-Guest Filesystem allows for shared folders between the host OS
and the guest OS in a Fusion or Workstation virtual environment. Do you wish
to enable this feature? [yes]
Before you can compile modules, you need to have the following installed...
make
gcc
kernel headers of the running kernel
Searching for GCC...
Detected GCC binary at "/usr/bin/gcc".
The path "/usr/bin/gcc" appears to be a valid path to the gcc binary.
Would you like to change it? [no]
Searching for a valid kernel header path...
Detected the kernel headers at "/lib/modules/3.19.0-15-generic/build/include".
The path "/lib/modules/3.19.0-15-generic/build/include" appears to be a valid
path to the 3.19.0-15-generic kernel headers.
Would you like to change it? [no]
make: Entering directory '/tmp/modconfig-qFEK5D/vmhgfs-only'
Using 2.6.x kernel build system.
/usr/bin/make -C /lib/modules/3.19.0-15-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/src/linux-headers-3.19.0-15-generic'
CC [M] /tmp/modconfig-qFEK5D/vmhgfs-only/dir.o
CC [M] /tmp/modconfig-qFEK5D/vmhgfs-only/rpcout.o
In file included from /tmp/modconfig-qFEK5D/vmhgfs-only/./shared/vmware.h:39:0,
from /tmp/modconfig-qFEK5D/vmhgfs-only/rpcout.c:43:
/tmp/modconfig-qFEK5D/vmhgfs-only/./shared/vm_assert.h:259:0: warning: "DEPRECATED" redefined
#define DEPRECATED(_fix) do {} while (0)
^
In file included from include/linux/kernel.h:13:0,
from /tmp/modconfig-qFEK5D/vmhgfs-only/./shared/kernelStubs.h:36,
from /tmp/modconfig-qFEK5D/vmhgfs-only/rpcout.c:33:
include/linux/printk.h:103:0: note: this is the location of the previous definition
#define DEPRECATED "[Deprecated]: "
^
CC [M] /tmp/modconfig-qFEK5D/vmhgfs-only/hgfsUtil.o
In file included from /tmp/modconfig-qFEK5D/vmhgfs-only/hgfs.h:40:0,
from /tmp/modconfig-qFEK5D/vmhgfs-only/hgfsUtil.h:55,
from /tmp/modconfig-qFEK5D/vmhgfs-only/hgfsUtil.c:33:
/tmp/modconfig-qFEK5D/vmhgfs-only/./shared/vm_assert.h:259:0: warning: "DEPRECATED" redefined
#define DEPRECATED(_fix) do {} while (0)
^
In file included from include/linux/kernel.h:13:0,
from include/linux/list.h:8,
from include/linux/preempt.h:10,
from include/linux/spinlock.h:50,
from include/linux/seqlock.h:35,
from include/linux/time.h:5,
from /tmp/modconfig-qFEK5D/vmhgfs-only/hgfsUtil.h:32,
from /tmp/modconfig-qFEK5D/vmhgfs-only/hgfsUtil.c:33:
include/linux/printk.h:103:0: note: this is the location of the previous definition
#define DEPRECATED "[Deprecated]: "
^
In file included from /tmp/modconfig-qFEK5D/vmhgfs-only/hgfs.h:40:0,
from /tmp/modconfig-qFEK5D/vmhgfs-only/hgfsProto.h:37,
from /tmp/modconfig-qFEK5D/vmhgfs-only/dir.c:37:
/tmp/modconfig-qFEK5D/vmhgfs-only/./shared/vm_assert.h:259:0: warning: "DEPRECATED" redefined
#define DEPRECATED(_fix) do {} while (0)
^
In file included from include/linux/kernel.h:13:0,
from include/linux/list.h:8,
from include/linux/module.h:9,
from /tmp/modconfig-qFEK5D/vmhgfs-only/dir.c:29:
include/linux/printk.h:103:0: note: this is the location of the previous definition
#define DEPRECATED "[Deprecated]: "
^
CC [M] /tmp/modconfig-qFEK5D/vmhgfs-only/cpName.o
CC [M] /tmp/modconfig-qFEK5D/vmhgfs-only/message.o
/tmp/modconfig-qFEK5D/vmhgfs-only/dir.c: In function ‘HgfsPackDirOpenRequest’:
/tmp/modconfig-qFEK5D/vmhgfs-only/dir.c:417:26: error: ‘struct file’ has no member named ‘f_dentry’
file->f_dentry) < 0) {
^
/tmp/modconfig-qFEK5D/vmhgfs-only/dir.c: In function ‘HgfsDirLlseek’:
/tmp/modconfig-qFEK5D/vmhgfs-only/dir.c:707:32: error: ‘struct file’ has no member named ‘f_dentry’
struct dentry *dentry = file->f_dentry;
^
In file included from /tmp/modconfig-qFEK5D/vmhgfs-only/dir.c:39:0:
/tmp/modconfig-qFEK5D/vmhgfs-only/dir.c: In function ‘HgfsReaddirNextEntry’:
/tmp/modconfig-qFEK5D/vmhgfs-only/dir.c:993:31: error: ‘struct file’ has no member named ‘f_dentry’
si = HGFS_SB_TO_COMMON(file->f_dentry->d_inode->i_sb);
^
/tmp/modconfig-qFEK5D/vmhgfs-only/module.h:78:62: note: in definition of macro ‘HGFS_SB_TO_COMMON’
#define HGFS_SB_TO_COMMON(sb) ((HgfsSuperInfo *)(sb)->s_fs_info)
^
/tmp/modconfig-qFEK5D/vmhgfs-only/dir.c:1082:26: error: ‘struct file’ has no member named ‘f_dentry’
*entryIno = file->f_dentry->d_inode->i_ino;
^
In file included from /tmp/modconfig-qFEK5D/vmhgfs-only/dir.c:30:0:
/tmp/modconfig-qFEK5D/vmhgfs-only/dir.c:1088:44: error: ‘struct file’ has no member named ‘f_dentry’
*entryIno = compat_parent_ino(file->f_dentry);
^
/tmp/modconfig-qFEK5D/vmhgfs-only/./shared/compat_fs.h:120:46: note: in definition of macro ‘compat_parent_ino’
#define compat_parent_ino(dentry) parent_ino(dentry)
^
/tmp/modconfig-qFEK5D/vmhgfs-only/dir.c:1093:52: error: ‘struct file’ has no member named ‘f_dentry’
*entryIno = HgfsGetFileInode(&entryAttrs, file->f_dentry->d_inode->i_sb);
^
/tmp/modconfig-qFEK5D/vmhgfs-only/dir.c: In function ‘HgfsDoReaddir’:
/tmp/modconfig-qFEK5D/vmhgfs-only/dir.c:1172:13: error: ‘struct file’ has no member named ‘f_dentry’
!(file->f_dentry) ||
^
/tmp/modconfig-qFEK5D/vmhgfs-only/dir.c:1173:13: error: ‘struct file’ has no member named ‘f_dentry’
!(file->f_dentry->d_inode)) {
^
scripts/Makefile.build:257: recipe for target '/tmp/modconfig-qFEK5D/vmhgfs-only/dir.o' failed
make[2]: *** [/tmp/modconfig-qFEK5D/vmhgfs-only/dir.o] Error 1
make[2]: *** Waiting for unfinished jobs....
In file included from /tmp/modconfig-qFEK5D/vmhgfs-only/backdoor.h:30:0,
from /tmp/modconfig-qFEK5D/vmhgfs-only/message.c:54:
/tmp/modconfig-qFEK5D/vmhgfs-only/./shared/vm_assert.h:259:0: warning: "DEPRECATED" redefined
#define DEPRECATED(_fix) do {} while (0)
^
In file included from include/linux/kernel.h:13:0,
from /tmp/modconfig-qFEK5D/vmhgfs-only/./shared/kernelStubs.h:36,
from /tmp/modconfig-qFEK5D/vmhgfs-only/message.c:45:
include/linux/printk.h:103:0: note: this is the location of the previous definition
#define DEPRECATED "[Deprecated]: "
^
Makefile:1394: recipe for target '_module_/tmp/modconfig-qFEK5D/vmhgfs-only' failed
make[1]: *** [_module_/tmp/modconfig-qFEK5D/vmhgfs-only] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-3.19.0-15-generic'
Makefile:130: recipe for target 'vmhgfs.ko' failed
make: *** [vmhgfs.ko] Error 2
make: Leaving directory '/tmp/modconfig-qFEK5D/vmhgfs-only'
The filesystem driver (vmhgfs module) is used only for the shared folder
feature. The rest of the software provided by VMware Tools is designed to work
independently of this feature.
If you wish to have the shared folders feature, you can install the driver by
running vmware-config-tools.pl again after making sure that gcc, binutils, make
and the kernel sources for your running kernel are installed on your machine.
These packages are available on your distribution's installation CD.
[ Press Enter key to continue ]Same issue. Apparently the VMWare Tools for Linux just haven't been updated for the newest versions of the Linux kernel.
Now that Ubuntu 15.04 has been officially released I'd guess a new version of VMWare Tools will be released shortly. I hope somebody from VMWare can give us a window of when we can expect this to happen. -
No Drag-n-Drop feature for my mounted Adobe Drive in my Adobe Bridge CC
I've developed a custom Drive Connector for our storage server. In Adobe Bridge CC, after connecting and auto-mounting to our server through Adobe Drive 5, there is no Drag-n-Drop feature for my data inside the mounted drive. But, if I browse other directories of my Mac with Bridge, all files are draggable. What could be the problem?
It's quite strange! Because, files within my mounted drive are draggable through Adobe Bridge CS6, but not in Adobe Bridge CC !!!
My configuration:
Mac OSX 10.9.2
Adobe Bridge CC 6.0.1.6
Adobe Drive 5.0.2.16
Our own custom Drive connectorI too have discovered the lack of Drag-n-Drop support in Bridge when browsing assets provided by my Adobe Drive connector. I have tried telling Drive that I support nearly all of the Drive features by adding "Capability" objects to the ConnectHandler's response object (including Capability.COPY and Capability.MOVE), but that had no effect; Bridge still refuses to let me drag an asset provided by the connector.
I would very much like to know what I have to do in order to provided Drag-n-Drop functionality. -
Compile in 1.5 JVM and run in 1.4 JVM, work?
1 - If i have a class that only uses generic and other features that are only useful for compile-time, is it possible to run compiled classes in 1.5 JVM in 1.4 JVM?
2 - If i'm right, the JVM 1.5 features that are useful for compile-time, are removed in the classes. For instance, the generic types that we use in java classes disappear in the classes files. Is this true?
Thanks,2 - If i'm right, the JVM 1.5 features that are
useful for compile-time, are removed in the classes.
For instance, the generic types that we use in java
classes disappear in the classes files. Is this
true?Not entirely.
If you do List<String> list = new ArrayList<String>();, then the <String> part is not kept. It's just a List.
But in the definition of the List interface, ArrayList class, etc., the fact that they take type parameters, and where, is kept. It has to be. How else could you even do List<String> in the first place? -
I do not know if this has been published before. I reviewed Director 12 and I am almost certain that the following list of features are not currently available with the new release of Adobe Director. I have been using director for years, some of these features become available with the use of Xtras, but it will be nice for Director to support these features natively:
Printing capability - A feature that will allow authors to implement the option of printing cast members or sprites (images or text)
Audio recording capability - An option to record to either a cast member or a file and also llow the user to choose the audio recording device.
Video recording capability - An option that will allow to record video to a file.
Feel free to add to this list.Access to the iPod music library.
Access to cameras.
Access to location services.
WebKit renderer.
iOS interface tool option added to classic, default and flash in the tool palette.
I don't think any of these should be possible: Director's iOS apps are actually .dcr (Shockwave) files that runs in a wrapper.
It's like an iOS app is already running inside a WebKit HTML page...
That's too bad, I know. -
How to find timestamp of packege/package body compiled in last 15 days
Hi all,
I would like to find the time stamp of package/package body compiled in the last 15 days.
Is there any feature, which will log all the compilation time stamp of a particular package or package body.
If so, please provide the query.
version : Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production
Thanks
RaghuYou can check the same from ALL_OBJECTs/USER_OBJECTS/DBA_OBJECTS.
In this views,
column CREATED always shows its created date & time.
LAST_DDL_TIME always shows last compiled time also it change if you run create or replace
TIMESTAMP will give you last change i.e. create OR replace time,
create package temp_pkg (v number;
sp_procedure());
select object_name,object_type, created, last_ddl_time, timestamp from all_objects
where object_type in ('PACKAGE','PACKAGE BODY')and object_name ='TEMP_PKG';
OBJECT_NAME OBJECT_TYPE CREATED LAST_DDL_TIME TIMESTAMP
TEMP_PKG PACKAGE 11/12/2012 6:07:18 PM 11/12/2012 6:07:18 PM 2012-11-12:18:07:18
alter package temp_pkg compile;
select object_name,object_type, created, last_ddl_time, timestamp from all_objects
where object_type in ('PACKAGE','PACKAGE BODY')and object_name ='TEMP_PKG';
OBJECT_NAME OBJECT_TYPE CREATED LAST_DDL_TIME TIMESTAMP
TEMP_PKG PACKAGE 11/12/2012 6:07:18 PM 11/12/2012 6:08:19 PM 2012-11-12:18:07:18
create or replace package temp_pkg (v number;
sp_procedure());
select object_name,object_type, created, last_ddl_time, timestamp from all_objects
where object_type in ('PACKAGE','PACKAGE BODY')and object_name ='TEMP_PKG';
OBJECT_NAME OBJECT_TYPE CREATED LAST_DDL_TIME TIMESTAMP
TEMP_PKG PACKAGE 11/12/2012 6:07:18 PM 11/12/2012 6:10:00 PM 2012-11-12:18:10:00
alter package temp_pkg compile;
select object_name,object_type, created, last_ddl_time, timestamp from all_objects
where object_type in ('PACKAGE','PACKAGE BODY')and object_name ='TEMP_PKG';
OBJECT_NAME OBJECT_TYPE CREATED LAST_DDL_TIME TIMESTAMP
TEMP_PKG PACKAGE 11/12/2012 6:07:18 PM 11/12/2012 6:11:07 PM 2012-11-12:18:10:00For packages/package body compiled/created/replaced in last 15 days you can check with below query.
select object_name,object_type, created, last_ddl_time, timestamp
from all_objects
where object_type in ('PACKAGE','PACKAGE BODY')and (sysdate-last_ddl_time)<=15 ;Edited by: myOra_help on Nov 12, 2012 6:45 PM -
Do new ODAC 11 feature work against Database 10.2
Hi,
Do features new in ODAC 11 work against Database 10.2. I'm mainly interested in "End-to-End Tracing using Action and Module attributes"
ThanksHere's a real quick and dirty knock up using ODAC 2.111.6.20 against a 10.2.0.3 database:
using System;
using System.Data;
using Oracle.DataAccess.Client;
using Oracle.DataAccess.Types;
namespace Miscellaneous
class Program
static void Main(string[] args)
string constr = "User Id=scott; " +
"Password=tiger; " +
"Data Source=lt10gr2; " +
"Pooling=false; " +
"Enlist=false";
OracleConnection con = new OracleConnection(constr);
con.Open();
con.ActionName = "MyAction1";
con.ModuleName = "MyModule1";
OracleCommand cmd1 = con.CreateCommand();
cmd1.CommandText = "select user from dual";
OracleDataReader dr = cmd1.ExecuteReader();
while (dr.Read()) ;
con.ActionName = "MyAction2";
con.ModuleName = "MyModule2";
OracleCommand cmd2 = con.CreateCommand();
cmd2.CommandText = "select sysdate from dual";
dr = cmd2.ExecuteReader();
while (dr.Read()) ;
Console.WriteLine("ENTER to continue...");
Console.ReadLine();
}I enabled tracing for the session and here are a couple of snippets from the trace file:
*** ACTION NAME:(MyAction1) 2008-01-24 21:08:01.033
*** MODULE NAME:(MyModule1) 2008-01-24 21:08:01.033
-- snip --
*** ACTION NAME:(MyAction2) 2008-01-24 21:08:01.049
*** MODULE NAME:(MyModule2) 2008-01-24 21:08:01.049
...Whilst obviously not extensive, I think this is the expected result...
- Mark
EDIT:
Just to be clear... this feature works with previous releases of the database; however, there are other features exposed via ODP.NET (or available to ODP.NET) such as the client side cache which will not work with previous releases. Possibly being pedantic, but thought it might be a good idea to state that anyway.
- Mark -
What is the advantage and features of having a sky...
what are the cost advantages of having a skype phone number and its features ?
Cheers HarveyPro:
By pre-compiling your JSPs you don't need a java compiler on the server - just a jre.
The result? No java compiler on the server means a potential security hole patched - people can't just write and deploy jsp's willy nilly on the server.
You KNOW that all your JSPs compile before you visit them - because you have compiled them all :-). It won't fail because of a stupid spelling miskate that prevents compilation. That doesn't mean they will run without error of course...
Con:
Compiling the JSPs ties them to a particular server - unless you take the runtime along with them. -
It's helpful for Mozilla's engineers to be able to measure how Firefox behaves in the real world. The Telemetry feature provides this capability by sending performance and usage info to us. As you use Firefox, Telemetry measures and collects non-personal information, such as memory consumption, responsiveness timing and feature usage. It then sends this information to Mozilla on a daily basis and we use it to make Firefox better for you.
Telemetry is an opt-in feature. Bring it to meHi Terrancecallins,
I understand that you would like to opt-in for the Telemetry feature in your Firefox browser. Thank you for your interest in helping to make Firefox better!
Here is the help article explaining how to turn on this feature:
* [[Send performance data to Mozilla to help improve Firefox]]
Please let us know if you have any other questions.
Thanks,
- Ralph -
Hi,
We use the remote compilation feature of LabVIEW FPGA. When compiling code for NI-5640R recently,
the remote server reported that the compilation was successful, however the client gave a message
suggesting a communication failure. The next time we again tried to compile the VI (with the same
client/server configuration) and the client reported success (in 5 minutes or less) while the server
remained Idle.
The report shows the the first try as the 'Start Time', and the 'End Time' corresponds to the
second try (which was couple days later in this case). If the reason for failure first time was
a network problem and the second time LabVIEW FPGA Compile Server was able to pull the files
already there, it's a pretty good feature !
Thanks.Hi manikg
I believe what you saw is to be expected. If the network connection is lost between the client and the server, the client should error out. The server should continue on its merry way to completion of its task.
Unfortunately, on its own, the server does not know enough to push the compile binary file back to the client.
When you try to compile again with the exact same project and code, the server will see if it has recently compiled this exact LV FPGA code and has the binary file available. If the FPGA code is exactly the same, it pushes the previously compiled binary file to the client immediately.
If the server thinks there is a something different in the new compile request, it goes ahead and starts a new compilation.
Jerry -
Jolz: uses a CPU feature which is not available?
First lines from m000 trace after the header:
*** 2009-03-30 16:34:30.780
*** SESSION ID:(1565.8) 2009-03-30 16:34:30.780
*** CLIENT ID:() 2009-03-30 16:34:30.780
*** SERVICE NAME:(SYS$BACKGROUND) 2009-03-30 16:34:30.780
*** MODULE NAME:(MMON_SLAVE) 2009-03-30 16:34:30.780
*** ACTION NAME:(JAVAVM JIT slave action) 2009-03-30 16:34:30.780
jolz: Compiled code for java/util/HashMap.<init>; uses a CPU feature which is not available
jolz: Compiled code for java/util/HashMap.resize; uses a CPU feature which is not available
jolz: Compiled code for java/util/HashMap.unmaskNull; uses a CPU feature which is not available
jolz: Compiled code for java/util/HashMap$Entry.getKey; uses a CPU feature which is not available
the last few entries are:
jolz: Compiled code for oracle/aurora/zephyr/backend/LiveLIRTemps$EnsureLoserLiveRangeIterator.apply; uses a CPU feature which is not available
jolz: Compiled code for oracle/aurora/zephyr/backend/LiveLIRTemps$GenBitSetIterator.apply; uses a CPU feature which is not available
This eventually leads to ORA-07445: [joe_run_vm()+15316] [SIGSEGV] [ADDR:0x24000] [PC:0x33FAB74] [Address not mapped to object] []
What is causing the "CPU feature which is not available" messages to be reported?
Thank for any assistance.
TraceyHi Tracy,
This typically means that the JIT has persisted compiled code that was built on one set of hardware that may use chipset features that are not available on the hardware at runtime. An example of this might be if the code were originally compiled on a modern x86 chip and makes use of SSE2 instructions, but then is asked to later run on old Pentium hardware without such instructions.
Regardless, it should not lead to ORA-7445. Can you please file an SR with your exact hardware description as well as tracefiles and also description of your deployment (e.g. wehther this database was migrated from one machine to another, etc...)
In the meantime, a likely workaround for you would be to connect as SYS and issue:
TRUNCATE TABLE SYS.JAVA$MC$
and then restart the instance.
thanks,
-Rob
JVM development -
Hello,
I've installed Arch in a VM running on VMware Fusion 4. Out of the box it doesn't fit the resolution to the window so if I go fullscreen it gets ugly. When I try to install vmware-tools I get an error:
[Fleet@mba vmware-tools-distrib]$ sudo ./vmware-install.pl
Creating a new VMware Tools installer database using the tar4 format.
Installing VMware Tools.
In which directory do you want to install the binary files?
[/usr/bin]
What is the directory that contains the init directories (rc0.d/ to
rc6.d/)? /etc/rc.d/vmware.d
What is the directory that contains the init scripts?
[/etc/rc.d/vmware.d] /etc/rc.d
In which directory do you want to install the daemon files?
[/usr/sbin]
In which directory do you want to install the library files?
[/usr/lib/vmware-tools]
In which directory do you want to install the documentation files?
[/usr/share/doc/vmware-tools]
The path "/usr/share/doc/vmware-tools" does not exist currently. This program
is going to create it, including needed parent directories. Is this what you
want? [yes]
The installation of VMware Tools 8.8.0 build-465068 for Linux completed
successfully. You can decide to remove this software from your system at any
time by invoking the following command: "/usr/bin/vmware-uninstall-tools.pl".
Before running VMware Tools for the first time, you need to configure it by
invoking the following command: "/usr/bin/vmware-config-tools.pl". Do you want
this program to invoke the command for you now? [yes]
Initializing...
Use of uninitialized value $subLevel in split at /usr/bin/vmware-config-tools.pl line 5324.
Use of uninitialized value $subLevel in concatenation (.) or string at /usr/bin/vmware-config-tools.pl line 5325.
Argument "0-ARCH" isn't numeric in multiplication (*) at /usr/bin/vmware-config-tools.pl line 4859.
Use of uninitialized value $subLevel in addition (+) at /usr/bin/vmware-config-tools.pl line 4859.
Making sure services for VMware Tools are stopped.
Stopping VMware Tools services in the virtual machine:
Guest operating system daemon: done
Virtual Printing daemon: done
Unmounting HGFS shares: done
Guest filesystem driver: done
/etc/rc.d/vmware-tools: line 1114: [: BASH=/bin/sh: integer expression expected
/etc/rc.d/vmware-tools: line 1114: [: BASH=/bin/sh: integer expression expected
/etc/rc.d/vmware-tools: line 1199: [: BASH=/bin/sh: integer expression expected
[EXPERIMENTAL] The VMware FileSystem Sync Driver (vmsync) is a new feature that
creates backups of virtual machines. Please refer to the VMware Knowledge Base
for more details on this capability. Do you wish to enable this feature?
[no]
Before you can compile modules, you need to have the following installed...
make
gcc
kernel headers of the running kernel
Searching for GCC...
Detected GCC binary at "/usr/bin/gcc".
The path "/usr/bin/gcc" appears to be a valid path to the gcc binary.
Would you like to change it? [no]
Searching for a valid kernel header path...
Detected the kernel headers at "/lib/modules/3.0-ARCH/build/include".
The path "/lib/modules/3.0-ARCH/build/include" appears to be a valid path to
the 3.0-ARCH kernel headers.
Would you like to change it? [no]
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmci-only'
make -C /lib/modules/3.0-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-3.0-ARCH'
CC [M] /tmp/vmware-root/modules/vmci-only/linux/driver.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciDatagram.o
CC [M] /tmp/vmware-root/modules/vmci-only/linux/vmciKernelIf.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciDriver.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciRoute.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciResource.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciHashtable.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciEvent.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciContext.o
CC [M] /tmp/vmware-root/modules/vmci-only/driverLog.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciQueuePair.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciQPair.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciDoorbell.o
LD [M] /tmp/vmware-root/modules/vmci-only/vmci.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-root/modules/vmci-only/vmci.mod.o
LD [M] /tmp/vmware-root/modules/vmci-only/vmci.ko
make[1]: Leaving directory `/usr/src/linux-3.0-ARCH'
make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vmci-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vmci-only'
cp -f vmci.ko ./../vmci.o
make: Leaving directory `/tmp/vmware-root/modules/vmci-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmci-only'
make -C /lib/modules/3.0-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-3.0-ARCH'
CC [M] /tmp/vmware-root/modules/vmci-only/linux/driver.o
CC [M] /tmp/vmware-root/modules/vmci-only/linux/vmciKernelIf.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciDatagram.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciDriver.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciRoute.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciResource.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciContext.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciHashtable.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciEvent.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciQPair.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciQueuePair.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciDoorbell.o
CC [M] /tmp/vmware-root/modules/vmci-only/driverLog.o
LD [M] /tmp/vmware-root/modules/vmci-only/vmci.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-root/modules/vmci-only/vmci.mod.o
LD [M] /tmp/vmware-root/modules/vmci-only/vmci.ko
make[1]: Leaving directory `/usr/src/linux-3.0-ARCH'
make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vmci-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vmci-only'
cp -f vmci.ko ./../vmci.o
make: Leaving directory `/tmp/vmware-root/modules/vmci-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vsock-only'
make -C /lib/modules/3.0-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-3.0-ARCH'
CC [M] /tmp/vmware-root/modules/vsock-only/linux/af_vsock.o
CC [M] /tmp/vmware-root/modules/vsock-only/linux/vsockAddr.o
CC [M] /tmp/vmware-root/modules/vsock-only/linux/util.o
CC [M] /tmp/vmware-root/modules/vsock-only/linux/notifyQState.o
CC [M] /tmp/vmware-root/modules/vsock-only/driverLog.o
CC [M] /tmp/vmware-root/modules/vsock-only/linux/stats.o
CC [M] /tmp/vmware-root/modules/vsock-only/linux/notify.o
LD [M] /tmp/vmware-root/modules/vsock-only/vsock.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-root/modules/vsock-only/vsock.mod.o
LD [M] /tmp/vmware-root/modules/vsock-only/vsock.ko
make[1]: Leaving directory `/usr/src/linux-3.0-ARCH'
make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vsock-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vsock-only'
cp -f vsock.ko ./../vsock.o
make: Leaving directory `/tmp/vmware-root/modules/vsock-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmxnet3-only'
make -C /lib/modules/3.0-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-3.0-ARCH'
CC [M] /tmp/vmware-root/modules/vmxnet3-only/vmxnet3_shm.o
CC [M] /tmp/vmware-root/modules/vmxnet3-only/vmxnet3_ethtool.o
CC [M] /tmp/vmware-root/modules/vmxnet3-only/vmxnet3_drv.o
LD [M] /tmp/vmware-root/modules/vmxnet3-only/vmxnet3.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-root/modules/vmxnet3-only/vmxnet3.mod.o
LD [M] /tmp/vmware-root/modules/vmxnet3-only/vmxnet3.ko
make[1]: Leaving directory `/usr/src/linux-3.0-ARCH'
make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vmxnet3-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vmxnet3-only'
cp -f vmxnet3.ko ./../vmxnet3.o
make: Leaving directory `/tmp/vmware-root/modules/vmxnet3-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/pvscsi-only'
make -C /lib/modules/3.0-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-3.0-ARCH'
CC [M] /tmp/vmware-root/modules/pvscsi-only/pvscsi.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-root/modules/pvscsi-only/pvscsi.mod.o
LD [M] /tmp/vmware-root/modules/pvscsi-only/pvscsi.ko
make[1]: Leaving directory `/usr/src/linux-3.0-ARCH'
make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/pvscsi-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/pvscsi-only'
cp -f pvscsi.ko ./../pvscsi.o
make: Leaving directory `/tmp/vmware-root/modules/pvscsi-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmmemctl-only'
make -C /lib/modules/3.0-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-3.0-ARCH'
CC [M] /tmp/vmware-root/modules/vmmemctl-only/backdoorGcc64.o
CC [M] /tmp/vmware-root/modules/vmmemctl-only/os.o
CC [M] /tmp/vmware-root/modules/vmmemctl-only/vmballoon.o
LD [M] /tmp/vmware-root/modules/vmmemctl-only/vmmemctl.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-root/modules/vmmemctl-only/vmmemctl.mod.o
LD [M] /tmp/vmware-root/modules/vmmemctl-only/vmmemctl.ko
make[1]: Leaving directory `/usr/src/linux-3.0-ARCH'
make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vmmemctl-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vmmemctl-only'
cp -f vmmemctl.ko ./../vmmemctl.o
make: Leaving directory `/tmp/vmware-root/modules/vmmemctl-only'
The VMware Host-Guest Filesystem allows for shared folders between the host OS
and the guest OS in a Fusion or Workstation virtual environment. Do you wish
to enable this feature? [yes]
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmci-only'
make -C /lib/modules/3.0-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-3.0-ARCH'
CC [M] /tmp/vmware-root/modules/vmci-only/linux/driver.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciDatagram.o
CC [M] /tmp/vmware-root/modules/vmci-only/linux/vmciKernelIf.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciContext.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciDriver.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciDoorbell.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciHashtable.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciResource.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciRoute.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciQueuePair.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciEvent.o
CC [M] /tmp/vmware-root/modules/vmci-only/driverLog.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciQPair.o
LD [M] /tmp/vmware-root/modules/vmci-only/vmci.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-root/modules/vmci-only/vmci.mod.o
LD [M] /tmp/vmware-root/modules/vmci-only/vmci.ko
make[1]: Leaving directory `/usr/src/linux-3.0-ARCH'
make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vmci-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vmci-only'
cp -f vmci.ko ./../vmci.o
make: Leaving directory `/tmp/vmware-root/modules/vmci-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmhgfs-only'
make -C /lib/modules/3.0-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-3.0-ARCH'
CC [M] /tmp/vmware-root/modules/vmhgfs-only/message.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/cpName.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/rpcout.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/link.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/filesystem.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/dentry.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/module.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/file.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/stubs.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/request.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/hgfsUtil.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/tcp.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/backdoor.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/vmci.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/transport.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/bdhandler.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/page.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/cpNameLinux.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/dir.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/super.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/fsutil.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/hgfsBd.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/backdoorGcc64.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/hgfsEscape.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/inode.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/cpNameLite.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/kernelStubsLinux.o
LD [M] /tmp/vmware-root/modules/vmhgfs-only/vmhgfs.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-root/modules/vmhgfs-only/vmhgfs.mod.o
LD [M] /tmp/vmware-root/modules/vmhgfs-only/vmhgfs.ko
make[1]: Leaving directory `/usr/src/linux-3.0-ARCH'
make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vmhgfs-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vmhgfs-only'
cp -f vmhgfs.ko ./../vmhgfs.o
make: Leaving directory `/tmp/vmware-root/modules/vmhgfs-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmxnet-only'
make -C /lib/modules/3.0-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-3.0-ARCH'
CC [M] /tmp/vmware-root/modules/vmxnet-only/vmxnet.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-root/modules/vmxnet-only/vmxnet.mod.o
LD [M] /tmp/vmware-root/modules/vmxnet-only/vmxnet.ko
make[1]: Leaving directory `/usr/src/linux-3.0-ARCH'
make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vmxnet-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vmxnet-only'
cp -f vmxnet.ko ./../vmxnet.o
make: Leaving directory `/tmp/vmware-root/modules/vmxnet-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmblock-only'
make -C /lib/modules/3.0-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-3.0-ARCH'
CC [M] /tmp/vmware-root/modules/vmblock-only/linux/stubs.o
CC [M] /tmp/vmware-root/modules/vmblock-only/linux/dbllnklst.o
CC [M] /tmp/vmware-root/modules/vmblock-only/linux/file.o
CC [M] /tmp/vmware-root/modules/vmblock-only/linux/block.o
CC [M] /tmp/vmware-root/modules/vmblock-only/linux/module.o
CC [M] /tmp/vmware-root/modules/vmblock-only/linux/super.o
CC [M] /tmp/vmware-root/modules/vmblock-only/linux/inode.o
CC [M] /tmp/vmware-root/modules/vmblock-only/linux/control.o
CC [M] /tmp/vmware-root/modules/vmblock-only/linux/filesystem.o
CC [M] /tmp/vmware-root/modules/vmblock-only/linux/dentry.o
LD [M] /tmp/vmware-root/modules/vmblock-only/vmblock.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-root/modules/vmblock-only/vmblock.mod.o
LD [M] /tmp/vmware-root/modules/vmblock-only/vmblock.ko
make[1]: Leaving directory `/usr/src/linux-3.0-ARCH'
make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vmblock-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vmblock-only'
cp -f vmblock.ko ./../vmblock.o
make: Leaving directory `/tmp/vmware-root/modules/vmblock-only'
!!! [EXPERIMENTAL] !!!
VMware automatic kernel modules enables automatic building and installation of
VMware kernel modules at boot they are not already present. By selecting yes,
you will be enabling this experimental feature. You can always disable this
feature by re-running vmware-config-tools.pl.
Would you like to enable VMware automatic kernel modules?
[no]
Detected X server version 1.10.4
Distribution provided drivers for Xorg X server are used.
Skipping X configuration because X drivers are not included.
Warning: This script could not find mkinitrd or update-initramfs and cannot
remake the initrd file!
Starting VMware Tools services in the virtual machine:
Switching to guest configuration: done
Paravirtual SCSI module: done
Guest memory manager: done
/etc/rc.d/vmware-tools: line 1114: [: BASH=/bin/sh: integer expression expected
VM communication interface: failed
VM communication interface socket family: failed
/etc/rc.d/vmware-tools: line 1114: [: BASH=/bin/sh: integer expression expected
Blocking file system: done
VMware User Agent: done
/etc/rc.d/vmware-tools: line 1199: [: BASH=/bin/sh: integer expression expected
Guest operating system daemon: done
Virtual Printing daemon: done
Unable to start services for VMware Tools
Execution aborted.
I can't figure out what to do different. Do you have any suggestions? I have also tried open-vm-tools but resolution auto switch and the other functionality didn't seem to work for me.
Last edited by Fleet (2011-09-25 15:48:14)I am evaluating Virtualbox as an alternative but Arch performes sluggish in VB though it allows me to run fullscreen with native resolution (1440x900).
Last edited by Fleet (2011-10-14 19:56:06) -
After-market headphones with hot keys?
So the stock headphones come with the ability to pause music and skip to next track (among other things) via a built-in clicker. I wonder if this means there are other features that can be exposed via after-market headphones.
Since I listen to podcasts and audiobooks, I'd like to be able to quickly go back and forward within the track via a headphone "hot key". Most important is going back say 10 seconds if I miss something due do noises nearby. This is more important on iPhone than on iPod because the touch-interface for ff/rw on long podcast/audiobook tracks is not as good as using the old click-wheel.
I don't expect Apple will add these features to their stock headphones since they like to keep things simple, but if they exposed this capability via the headphone "API" (seems it might already be there), then other vendors could supply headphones with these sorts of hot keys for geeks like me.
Anyone know if these sorts of actions are exposed via headphone jack and if any vendors are planning to add headphones with such capabilities?Unfortunately htting the esc key does not solve it. Does the 3-button method only work for certain versions and/or platforms? As I mentioned, while holding them down while launching it only pops up the Scratch Disk Preferences.
Maybe you are looking for
-
How can I pass empty value in URL Parameter
Hi, I am passing different URL parameters to one page, to filter the recordset on that page. How can I pass an empty value in the URL parameter so that the recordset in unfiltered? The URL parameter is based on one field of the database: ContentType.
-
I'm using YouTube Video and Audio Downloader. Sometimes the audio and video files combine automatically, sometimes they don't - remaining as separate " DASH - .m4a and DASH - .mp4 ". It used to be that when this would happen I could open up a "ffmpeg
-
HiI need help connecting the MacBook pro to the HDTV. I have the attachment and have it connected but I want to play videos or video from the Internet and all I can see is the background screen of the Mac. Hope the solution is simple :)
-
Deleting tank dips in O4_tiger.
How do I delete a Tank dip entry in Transaction 04_TIGER. I created tank dip but when I go to change tank dip option and bring up the selected dip that need deleting, I tick the DD box , select delete line option and save. Tank dip disapperes but wh
-
Wish to keep always 2 years of data on the cube
Hi Experts, we wish to keep always 2 years of data on the cube and archive the data after it is 2 years old. Any thought on this is appreciated. Thanks, Varun.