Sponsored Content
Operating Systems OS X (Apple) MacOS 10.15 Catalina Crashes and Freezes on Boot Post 303037709 by vbe on Saturday 10th of August 2019 05:36:47 AM
Old 08-10-2019
I wonder if its not to do with some untested hardware issue since apple using intel processors seem to have changed regularly the inners, things less current when under powerPC ( I still have 2 of them...). I am trying to figure out what in high sierra can make my powerbook pro of 2011 over heat... ( because I burnt my motherboard (graphics...) beginning July ) or go berserk from time to time, I have just assembled a new one but this time a late 2011 motherboard after buying a 2012 for later usage, and again it reaches over 40 C after 15 minutes not doing anything special, the 2012 is already in mojave but so far not much time to play with as still sick and just finished a 3 weeks antibiotics treatment... but into as I dont know anything about the inners of the Mac Pro and mac mini but if like the laptops I would not be surprised... Not insisting for now as we have a heat wave passing just now and was 34C yesterday ( last time it was 36C here...) Monday 25C announced so I will try again...
AS now Im using my wife's ( my ex-hospital usage laptop...) Macbook air which is now under Mojave and am surprised that it stays cool doing exactly the same thing and yes it does heat when I start heavy usage but never like the Macbook pro which can exceed 45 after only 15 minutes when I use it seriously...
My idea was to investigate on the heating control, could it be faulty for my old HW and so not reacting in time? as like you before burning it did crash a few times without to me any reason and I could not see anything in the logs explaining except a panic but can't find the cause...
 

10 More Discussions You Might Find Interesting

1. Solaris

Catalina Analysis

How can I make analysis for catalina.out (2 Replies)
Discussion started by: Burhan
2 Replies

2. Solaris

Solaris 10 crashes upon boot after TUN driver installed

Hey! I compiled TUN 1.1 driver on my Solaris 10 64bit, and everything was working fine, all the commands for installation were successfull (add_drv, devfsadm -i tun ... etc.) and the driver was working fine as I got OpenVPN server up and running with successful clients attached. My only problem... (2 Replies)
Discussion started by: TomSu
2 Replies

3. Solaris

Log Rotation of Catalina.out

Hi, Recently i received a request to rotate logs of catalina.out (tomcat). The file size was about 807 MB. I used logadm to truncate the log ( -c ) and zip (-z 0) it. Everything worked fine, catalina.out.0.gz was created (22 MB) and the size of original catalina.out became 0kb. After... (2 Replies)
Discussion started by: Mack1982
2 Replies

4. Shell Programming and Scripting

Montioring Script Tomcat catalina.out

Hi, I need to monitor the tomcat log file called "Catalina.out" for any errors like out of memory,JDBC exceptions,broken pipe any other errors and exceptions The script should monitor this file and send a mail instantly and create a text file with errors day to day. Iam using Solaris... (3 Replies)
Discussion started by: chaithanyaa
3 Replies

5. OS X (Apple)

MacOS 10.15 (Catalina) switches from bash to zsh

Interestingly Apple has decided to switch the default shell for new users from bash to zsh in MacOS Catalina (10.15) Use zsh as the default shell on your Mac - Apple Support Another interesting fact is that Catalina also comes with /bin/dash (5 Replies)
Discussion started by: Scrutinizer
5 Replies

6. Programming

Python Screen Capture of RIGOL 1054Z on macOS Catalina Using NI-VISA

On the NI-VISA boards there has been some frustration where folks cannot get NI-VISA to work on macOS Catalina because Catalina (macOS 10.15.x) is "not supported" by NI-VISA (for many months, it seems). Currently, the README shows: NI-VISA 19.0 for macOS supports the following platforms: ... (10 Replies)
Discussion started by: Neo
10 Replies

7. Windows & DOS: Issues & Discussions

Poor Windows 10 Performance of Parallels Desktop 15 on macOS Catalina

Just a quick note for macOS users. I just installed (and removed) Parallels Desktop 15 Edition on my MacPro (2013) with 64GB memory and 12-cores, which is running the latest version of macOS Catalina as of this post. The reason for this install was to test some RIGOL test gear software which... (6 Replies)
Discussion started by: Neo
6 Replies

8. OS X (Apple)

Warning! Upgrade to Catalina 10.15.3 Crashes MacPro (2013) - Will Not Boot !

WARNING! Just upgraded my MacPro (2013) from Catalina 10.15.2 to 10.15.3. After the routine download and restart for upgrade installation, the Mac would not boot. Totally crashed. Now, I'm in the process of a 15 hour restore from my last time machine backup. I'm not very happy with... (3 Replies)
Discussion started by: Neo
3 Replies

9. Programming

A Slightly Better NTP Client for the ESP32 (ESPWROOM32) on macOS Catalina

Currently have two ESP8266 modules testing some Blynk apps, whereI'm not so happy with the Blynk business model for developers, but that's another story. So, with two of my ESP8266s currently "busy", I decided to work on the ESP32, and in particular the ESPWROOM32. I installed the... (0 Replies)
Discussion started by: Neo
0 Replies

10. OS X (Apple)

MacOS 10.15.2 Catalina display crash and system panic

MacPro (2013) 12-Core, 64GB RAM (today's crash): panic(cpu 2 caller 0xffffff7f8b333ad5): userspace watchdog timeout: no successful checkins from com.apple.WindowServer in 120 seconds service: com.apple.logd, total successful checkins since load (318824 seconds ago): 31883, last successful... (3 Replies)
Discussion started by: Neo
3 Replies
aylet(1)							  Music Software							  aylet(1)

NAME
aylet, xaylet - play Spectrum `.ay' music files SYNOPSIS
aylet/xaylet [-BehlmnNsS] [-A stopafter] [-F fadetime] [-t tracknum] [file1 [file2 ... ]] DESCRIPTION
aylet plays music files in the `.ay' format. These files are essentially wrappers around bits of Z80 code which play music on the Sinclair ZX Spectrum 128's sound hardware - the beeper, or the AY-3-8912 sound chip, or both. Files using the Amstrad CPC ports are also supported. `aylet' has a curses-based interface, and `xaylet' has an X-based one. OPTIONS
-A set stop-after time in seconds (this is the time at which tracks start fading out), or 0 to disable fading. The default is 180 sec- onds (3 minutes). -B use `ABC' stereo positions, rather than the default `ACB'. ACB effectively pushes channels A and B to the left and right (using a stereo delay), with C remaining central; ABC puts A and C to the left/right instead, leaving B central. -e force 8-bit playback, even if 16-bit is available. -F set fade-out time in seconds (the time tracks take to fade out). The default is 10 seconds. -h give terse usage help. -l list the contents of files (track names etc.) rather than playing them. -m use mono rather than the default stereo playback. -n rather than the usual interface, use a simple batch-playing tty style, a bit like mpg123. (Only works in the curses version.) -N use `narrow' stereo separation (so the channels sound closer together) rather than the default `wide' separation. -s output sample data to stdout rather than playing it; implies `-n'. The sample is 44.1kHz 16-bit stereo (or mono if using `-m'). Don't be surprised if the sample takes a little while to generate, as it still has to emulate the Z80. -S apply a pseudo-stereo effect to the beeper output. Works well in some cases, but can make things sound a bit shaky (or rather, more so than usual :-)). -t play only the specified track, then exit. (Strictly speaking, it starts playing the given track, and exits when any track fades out.) Mainly useful when playing a single file non-interactively. file1 etc. the file(s) to play. Currently these can only be specified on the command-line. BEHIND THE SCENES
The way aylet works may seem a little strange if you're not familiar with how the `.ay' format goes about things, so here's some background on how it all works. As mentioned above, the files basically contain chunks of machine code to run on an emulated Z80 with certain sound hardware. Since you're just running a program, you can't really fast-forward or rewind as such, but you can move between tracks specified in the file. (Some files only have one, but others have several.) The whole just-running-a-program thing leads to two other problems, too. You can't tell where a track ends, other than to see when the sound stops; what aylet does is to exit a track after 4 seconds of total silence. And a track may never end at all; aylet fades it out after 3 minutes by default. (Yes, 3 minutes be may too soon to allow some tracks to `finish', but you have to strike the balance somewhere, and it's only a default. Use `-A' or press `s' to change it.) KEYS
Both the curses-based and X-based interfaces use these keys (some of which are based on those used by XMMS): q or Esc exit the program. z previous track. x play. c pause. v stop. b next track. r restart track. Backspace or Delete previous file. Space next file. s increase stop-after time. S decrease stop-after time. Setting it to zero disables fading completely. f increase fade-out time. F decrease fade-out time. h enable/disable high-speed mode, playing four times as fast when enabled (in a way), as a sort of substitute for a real fast-forward control. In xaylet, you can also use the matching buttons for most of the above. When using `aylet -n', the interactivity is scaled down dramatically, leaving just the one control: Ctrl-C if the current track has been playing for less than half a second, exit the program; otherwise, skip to the next track. Note that the key used to do this is really whatever you have set up to generate a SIGINT signal, but it's generally Ctrl-C. EXAMPLES
To play all .ay files in the current directory: aylet *.ay or xaylet *.ay To convert ysfollin.ay to a mono sample in .wav format (requires `sox'): aylet -sm ysfollin.ay |sox -r 44100 -t sw - tune.wav BUGS
The AY is probably too loud relative to the beeper. This may be fixed in the next version, though it's more likely to be an option to choose between the current more reasonable balance and the real thing. :-) Several options which it could reasonably allow to be changed at runtime (e.g. AY stereo, beeper stereo, ACB vs. ABC) can't be at the moment. The X version is currently a bit too much like the curses one, at the expense of GUIness in some respects. SEE ALSO
fuse(1) AUTHOR
Russell Marks (rus@svgalib.org). The Z80 emulation was written by Ian Collier, for xz80. Chris Cox wrote the OpenBSD sound code. Matan Ziv-Av was partly responsible for the OSS sound code. Version 0.4 1st October, 2004 aylet(1)
All times are GMT -4. The time now is 12:47 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy