This is my system configuration.
System: Microsoft Windows 2000 5.00.2195 Service Pack 4
Computer: Intel Core 2 CPU 6320 @ 1.86Ghz AT/AT compatible 2.096.236KB
RAM
SoundCard: SoundMAX Integrated Digital HD Audio - Manufacturer:
AnalogDevices
Driver Version: 5.10.1.4100 provided by AnalogDevices
wow, I'm glad that this solved it. in case you still want audio output to
work, try defining the following environment variable before starting the
emulator:
set QEMU_AUDIO_IN_DRV=none
this will disable the Windows wave input audio driver, while still using
wave output (like M3) did. if this d
That's it!!
Launching the emulator with the -noaudio solves the problem.
About the error message "could not find \tools\adb.exe", the path was
set correctly, but I was having some error messages related with adb
("adb] * daemon not running. starting it now") so I though that may be
it could be re
ok, first the "could not find \tools\adb.exe" error message indicates that
you did not setup your SDK installation path in the plugin's preferences
panel.
that's why the plugin is searching the root directory for the adb executable
(and doesn't find it). this should be unrelated to your restart.
a
It's a hard reboot.
So do u think that may be the problem belongs to the computer?
Because I haven't seen any system adverts, the system restarts and
nothing seems to be wrong.
The only thing that seems to be wrong is the adb plugin. This is the
only related thing I have read about (see the err
as said previously, there is no good reason for this to happen. the emulator
is a normal application and never sends any message to Windows to order a
restart the machine. and since we can't reproduce it, can you provide us
with some additionnal details:
- is this a "hard reboot", i.e. the compute
Thanks, but that didn't solves the problem.
When I set the SDK path in the Eclipse (at the first time, just when I
open the "Android" tab) this messages appears:
[2008-03-27 14:57:19 - adb] Failed to get the adb version: Cannot run
program "\tools\adb.exe": CreateProcess error=3, The system can
Thanks, but that didn't solves the problem.
When I set the SDK path in the Eclipse (at the first time, just when I
open the "Android" tab) this messages appears:
[2008-03-27 14:57:19 - adb] Failed to get the adb version: Cannot run
program "\tools\adb.exe": CreateProcess error=3, The system can
Hi,
The message you are seeing is an DDMS console change it to android
console.Change it to android console.You can Run yor application normally
On Thu, Mar 27, 2008 at 4:45 PM, AMGG <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I have the same problem.
>
> Yesterday I upgraded my sdk from m3 to m5 a
Hi,
I have the same problem.
Yesterday I upgraded my sdk from m3 to m5 and when I tried to launch
the emulator, suddenly my computer restarts.
I did it before to wipe the data from the emulator (I forgot it) so I
skipped step 6...
Once I realized that I had forgotten step 6 I tried to do it, but
10 matches
Mail list logo
