Sponsored Content
Special Forums Windows & DOS: Issues & Discussions Poor Windows 10 Performance of Parallels Desktop 15 on macOS Catalina Post 303043280 by Neo on Thursday 23rd of January 2020 07:13:31 AM
Old 01-23-2020
Update:

I have RIGOL UltraScope working on macOS Catalina using Windows 10 in Parallels.

One of the tricks is to install RIGOL UltraSigma first and install UltraScope afterwards, launching UltraScope only from UltraSigma.

Poor Windows 10 Performance of Parallels Desktop 15 on macOS Catalina-sigma_scope_windows_parallelsjpg


This link (to PDF file) was helpful:

Rigol Software Installation and Use

It's slow running in the Parallels VM, but it works.... and so does other Windows only software for test gear.
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Samba on E3500 Poor Performance!!!

Hi you all, I have a BIG performance problem on an Sun E3500, the scenario is described below: I have several users (30) accessing via samba to the E3500 using an application built on Visual Foxpro from their Windows PC , the problem is that the first guy that logs in demands 30% of the E3500... (2 Replies)
Discussion started by: alex blanco
2 Replies

2. UNIX for Advanced & Expert Users

HW Raid poor io performance

Hello all We just built a storage cluster for our new xenserver farm. Using 3ware 9650SE raid controllers with 8 x 1TB WD sata disks in a raid 5, 256KB stripe size. While making first performance test on the local storage server using dd (which simulates the read/write access to the disk... (1 Reply)
Discussion started by: roli8200
1 Replies

3. AIX

Poor Performance of server

Hi, I am new registered user here in this UNIX forums. I am a new system administrator for AIX 6.1. One of our servers performs poorly every time our application (FINACLE) runs many processes/instances. (see below for topas snapshot) I use NMON or Topas to monitor the server utilization. I... (9 Replies)
Discussion started by: guzzelle
9 Replies

4. Solaris

Poor performance on an M3000

Hi We have an M3000 single physical processor and 8gb of memory running Solaris 10. This system runs two Oracle Databases one on Oracle 9i and One on Oracle 10g. As soon as the Oracle 10g database starts we see an immediate drop in system performance, for example opening an ssh session can... (6 Replies)
Discussion started by: gregsih
6 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. OS X (Apple)

MacOS 10.15 Catalina Crashes and Freezes on Boot

Sadly, I have turned off my access to the Apple Developers Beta program after installing macOS 10.15 Catalina a few days ago. After the install, I rebooted by MacBook Air and it "hard froze" and we were heading out of town so I grabbed a backup MBA running Mojave. Then, after getting back at... (10 Replies)
Discussion started by: Neo
10 Replies

7. 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

8. 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

9. 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
patchsvr(1M)						  System Administration Commands					      patchsvr(1M)

NAME
patchsvr - set up a Sun Update Connection Proxy SYNOPSIS
/usr/sbin/patchsvr setup [-c cache-location] [-d] [-h] [-l] [-p update-source-url] [-s pw-file-location] [-u user-name] [-x web-proxy- host:port] /usr/sbin/patchsvr start /usr/sbin/patchsvr stop /usr/sbin/patchsvr enable /usr/sbin/patchsvr disable DESCRIPTION
The patchsvr command enables you to set up a Sun Update Connection Proxy on your intranet. The setup subcommand configures the Sun Update Connection Proxy. The start and stop subcommands start and stop the Sun Update Connection Proxy. Finally, the enable and disable subcom- mands permit you to start up and prevent startup of the Sun Update Connection Proxy at boot time. The Sun Update Connection Proxy was previously called local patch server. Note - The Sun Update Connection Proxy supports client systems that use the Sun Update Connection, System Edition software and the Sun Patch Manager 2.0 software. A Sun Update Connection client system is not compatible with the older local patch server feature asso- ciated with the Sun Patch Manager 2.0 software. Configuring Your Sun Update Connection Proxy By default, Update Manager expects that your local systems are connected, via the Internet, to the Sun update server to be analyzed and to receive updates. By using a Sun Update Connection Proxy instead, you can minimize the Internet traffic and serve your local systems from a update server on your intranet. The system you choose to act as the Sun Update Connection Proxy must be running at least the Developer Solaris Software Group of the Solaris 10 Operating System. You must also install the Sun Update Manager 1.0 software and the Sun Update Connection Proxy software. The use of a Sun Update Connection Proxy addresses security concerns and reduces the amount Internet traffic between the Sun update server and your client systems. For instance, instead of having to download updates and metadata from the Sun update server to each of your systems, the data is downloaded to the Sun Update Connection Proxy the first time that a client system requests an update. After the update data is stored on your Sun Update Connection Proxy, the transfer of update data to your system for analysis is done over your intranet instead of over the Internet. You can configure a chain of update servers on your intranet. The last link in the chain of local servers can point to the Sun update server or to a local collection of updates. By using this chain of servers, an update download request from your system to its primary update server can be forwarded to other servers in the chain in an attempt to fulfill the request. So, if your system's primary server can- not locate an update, the server makes the same request of the next server in the chain to see if the update is stored there. If the update is found, it is downloaded to the system. If the update is not found, the request continues along the chain until the update is found or the terminal point in the chain is reached. Each server in the chain stores the updates found on another server in the chain based on the download request. So, an update that is not initially found on your local server will be downloaded to your local server and stored before being downloaded to the client system. Your Sun Update Connection Proxy must specify the source of updates to use. By default, the server obtains updates from the Sun update server, but it can also obtain updates from another update server in the chain or from a collection of updates on your system. You must specify the URL that points to the collection of updates. By default, the Sun update server is the source of updates. The URL is: https://getupdates.sun.com/solaris/ Note that this URL must appear as a single line. This URL must point to another server in the chain or to a collection of updates on the local system. This URL cannot be null. Starting and Stopping Your Sun Update Connection Proxy The patchsvr start command starts the Sun Update Connection Proxy. You can also enable the boot-time startup of the Sun Update Connection Proxy by running patchsvr enable. The patchsvr stop command stops the Sun Update Connection Proxy. You can also disable the boot-time startup of the Sun Update Connection Proxy by running patchsvr disable. Before you use your Sun Update Connection Proxy for the first time, you must run the patchsvr start command. Use these commands when you want to change the configuration of your Sun Update Connection Proxy. Before you use the patchsvr setup command to change the configuration parameter values, you must stop your Sun Update Connection Proxy. Then, you can update the configuration val- ues. Finally, you must restart the Sun Update Connection Proxy. OPTIONS
The following options are supported for the patchsvr setup command: -c cache-location Specifies the location of the server's cache, also known as the update repository. This is the directory in which downloaded updates are stored on the Sun Update Connection Proxy. You must specify a full path to the cache loca- tion. By default, the cache location is file:/var/sadm/spool/patchsvr. Ensure that this update repository has 2 Gbytes of free disk space available to store downloaded updates. -d Resets the Sun Update Connection Proxy configuration settings to the default values. -h Displays information about the command-line options. -l Lists the configuration settings for the update server. -p update-source-url Specifies the URL that points to the collection of updates. By default, the URL points to the Sun update server: https://getupdates.sun.com/solaris/ Note that this URL must appear as a single line. -s pw-file-location Specifies the path of the proxy password file in which you have stored your proxy password. You must put the password in a file rather than specifying it on the command line because command-line information is visible via the ps command. -u user-name Specifies the user name required for web proxy authentication. -x web-proxy-host:port Specifies the local web proxy. If the Sun Update Connection Proxy is behind a firewall, use this option to specify the web proxy that accesses the Internet. Get the name of the web proxy, web-proxy-host, and its port, port, from your system administrator or network administrator. The default port value is 8080. Do not use this option if you are accessing update data from a collection of updates on the Sun Update Connection Proxy. EXAMPLES
Example 1: Changing the Cache Location # patchsvr setup -c /var/update/cache Example 2: Specifying the Sun Update Server as the Source of Updates # patchsvr setup -p https://getupdates.sun.com/solaris/ The Sun update server is the default source of updates. Example 3: Specifying a Sun Update Connection Proxy as the Source of Updates # patchsvr setup -p http://updatesvr1:3816/solaris/ Specifies the system called updatesvr1, a Sun Update Connection Proxy, as the source of updates. Example 4: Specifying a CD as the Source of Updates # patchsvr setup -p file:/cdrom/cdrom0 Specifies the CD mounted from the first CD-ROM drive of the local system as the update source. Example 5: Specifying a Web Proxy # patchsvr setup -x webproxy:8080 Specifies the host name, webproxy, and port, 8080, of the web proxy that your Sun Update Connection Proxy uses to connect to the Internet. Example 6: Specifying a User Name and Password for Web Proxy Authentication # (umask 77 ; vi /tmp/password) # patchsvr setup -u terry -s /tmp/password # rm /tmp/password While in a subshell, you create a temporary file that is not readable by others and put the password in that file. Next, you specify the user name, terry, and location of the password file, /tmp/password, used to authenticate the web proxy that your Sun Update Connection Proxy uses to connect to the Internet. Then, you delete the temporary file now that the web proxy authentication is specified. Example 7: Resetting the Configuration Settings to the Default Values # patchsvr setup -d Example 8: Listing the Configuration Settings for Your Sun Update Connection Proxy # patchsvr setup -l Patch source URL: https://getupdates.sun.com/solaris/ Cache location: /var/sadm/spool/patchsvr Web proxy host name: mars Web proxy port number: 8080 Shows the configuration settings, which include information about the source of updates, the location of the cache directory, and, if needed, a web proxy and port. Example 9: Starting the Sun Update Connection Proxy # patchsvr start Example 10: Stopping the Sun Update Connection Proxy # patchsvr stop Stops your Sun Update Connection Proxy. While the update server is stopped, you can change the configuration settings for your Sun Update Connection Proxy, then restart it. Example 11: Enabling the Boot-Time Startup of the Sun Update Connection Proxy # patchsvr enable Example 12: Disabling the Boot-Time Startup of the Sun Update Connection Proxy # patchsvr disable ATTRIBUTES
See the attributes(5) man page for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWpsvru | +-----------------------------+-----------------------------+ |Interface Stability |Evolving | +-----------------------------+-----------------------------+ SEE ALSO
smpatch(1M), attributes(5) Sun Update Manager 1.0 Administration Guide SunOS 5.10 12 May 2005 patchsvr(1M)
All times are GMT -4. The time now is 01:29 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy