![]() The detailed system report from the "newer" zoom crash is still available. My subsequest posts are as "WCM", and use the new zoom account not tied to a google account. The original post (from "BillM") to this thread is mine. Follow the prompts to confirm you see yourself, hear a ringtone, and can record your voice using a microphone. Before deleting the zoom account tied to my google account, I posted the problem. The test will prompt you to join with audio or test your speaker and microphone. Each meeting has a unique 9, 10, or 11-digit number called a meeting ID that. Our solution offers the best video, audio, and screen-sharing experience across Zoom Rooms, Windows, Mac, iOS, Android, and H.323/SIP room systems. So I deleted my zoom account (tied to my google account), and created a new zoom account not tied to a google account. You can also join a test meeting to familiarize yourself with Zoom by using. Zoom unifies cloud video conferencing, simple online meetings, and cross platform group chat into one easy-to-use platform. When I originally experienced the problem, I saw the "Chrome_IOThread trap" in the system problem report, and wondered if the problem might have something to do with me using a google account to log in. ![]() ![]() I'll have to try a real zoom meeting with a friend in the near future. Curiously, zoom seemed to continued to work. That allowed me me to submit the crash report. I ninstalled the "new", and installed the "older" that you pointed me to.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |