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
Currently I don't care about the sound, so I will try your suggestion
in the future when I have more time (I have lost a lot of time with
this problem). But I will report it if it doesn't works.
Many thanks for ur help, has been very useful!
On 31 mar, 19:49, Digit <[EMAIL PROTECTED]> wrote:
> 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 doesn't work, let me know too.
>
> could you tell us more about your hardware and OS version ? which sound card
> do you have, what driver is it using, which version, on which OS version
> exactly ? this will help us diagnose the problem in the future.
>
> I don't think there is anything we can do here, the emulator only does
> normal Win32 API calls like waveInOpen() et al. these are certainly not
> supposed to reboot your machine.
>
> regarding the error messages:
>
> "could not find \tools\adb.exe" is printed by the Eclipse plugin when you
> don't setup the SDK path normally
>
> "[adb] * daemon not running. starting it now" is printed by the adb tool
> when it detects that the ADB server (i.e. the adb.exe background daemon) is
> not running. this is not an error message, just a normal one but it's good
> to print it for diagnostic reasons.
>
> a bug would be a message like "[adb] failed to start server" though
>
> On Mon, Mar 31, 2008 at 12:29 AM, AMGG <[EMAIL PROTECTED]> wrote:
>
> > 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 related.
>
> > Many thanks!!
>
> > On 28 mar, 22:12, Digit <[EMAIL PROTECTED]> wrote:
> > > 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 hard reboot is a nasty thing that can only be generated by a flaky
> > > hardware or driver. it's difficult to know why here, but one difference
> > > between the M5 and M3 emulator binaries is that the former tries to open
> > the
> > > Windows wave input at startup to implement audio recording (this feature
> > is
> > > however still broken in M5 for reasons to lenghty to explain there).
> > maybe
> > > this is triggering something in your system. can you try starting the
> > > emulator from the command-line with "emulator -noaudio" to see if this
> > > changes anything ?
>
> > > On Fri, Mar 28, 2008 at 12:43 PM, AMGG <[EMAIL PROTECTED]> wrote:
>
> > > > 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 error messages I mention
> > > > in the previous posts).
>
> > > > [2008-03-27 14:57:19 - adb] Failed to get the adb version: Cannot run
> > > > program "\tools\adb.exe": CreateProcess error=3, The system cannot
> > > > find the path specified
> > > > [2008-03-27 14:58:17 - adb] * daemon not running. starting it now *
> > > > [2008-03-27 15:48:12 - DeviceMonitor] Connection attempts: 1
> > > > [2008-03-27 15:48:14 - adb] * daemon not running. starting it now *
>
> > > > I think it should be some kind of incompatibility between my system
> > > > and m5, because before to install m5 all was running properly. Or some
> > > > problem with the adb plugin which makes my computer to crash... really
> > > > weird.
>
> > > > About the logs... do you mean system.log? I will take a look on
> > > > Monday (its the company pc)
>
> > > > Thanks!
>
> > > > On 28 mar, 17:47, Digit <[EMAIL PROTECTED]> wrote:
> > > > > 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 computer restarts immediately.
> > By
> > > > > contrast, with a "graceful restart", you will see all applications
> > > > windows
> > > > > closing, then the Windows shell exiting, then a few seconds where
> > the
> > > > > computer shut downs properly with only the "login background".
> > > > > or do you see the blue screen of death ?
>
> > > > > - is there anything in the system logs that indicate a fatal error
> > or
> > > > the
> > > > > reason for the restart ?
> > > > > there probably is something there that should explain what's
> > happening
>
> > > > > On Fri, Mar 28, 2008 at 9:46 AM, AMGG <[EMAIL PROTECTED]> wrote:
>
> > > > > > Hi ,
>
> > > > > > I have updated Android SDK from M3 to M5, each time I start the
> > > > > > emulator, my computer restarts. Can somebody please help me?
>
> > > > > > 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)
> > > > > > Once I realized that I had forgotten to wipe the data I tried to
> > do
> > > > > > it, but the
> > > > > > computer restarted again when I tried the command: "emulator
> > -wipe-
> > > > > > data" (the
> > > > > > computer restarts immediately)
>
> > > > > > After the computer restarts, I have this message in the Eclipse
> > > > > > console: "[2008-03-27 12:00:17 - adb] * daemon not running.
> > starting
> > > > > > it now *"
>
> > > > > > Any idea?
>
> > > > > > About my pc:
> > > > > > W2000 sp4, Intel core2 1.86Ghz, 2gb ram
>
> > > > > > I was posting on this thread, so you can found more details about
> > my
> > > > > > problem here:
>
> >http://groups.google.com/group/android-developers/browse_thread/threa.
> > > > ..
>
> > > > > > Thanks.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[EMAIL PROTECTED]
Announcing the new M5 SDK!
http://android-developers.blogspot.com/2008/02/android-sdk-m5-rc14-now-available.html
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
