怎样安装scratch2.0离线编辑器_百度经验
&&&&&&教育怎样安装scratch2.0离线编辑器？听语音1234567
百度经验:scratch2.0跟以前的版本scratch1.4相比，多了一个adobeair服务，可以方便用户将scratch程序在不同的操作系统下运行，因此安装的时候同学们比以往觉得困难，下面我们一起来看看怎样安装它。百度经验:电脑，scratch2.0软件百度经验:1将下载好后的安装包解压；2这是解压后的文件；3双击scratch下载包.air，4正在准备安装应用程序；5确认安装；6将安装路径c：改为d：，然后继续；7开始安装程序；8安装完毕自动启动程序进入工作界面，如果有更新文件，会提示现在是否更新；9点update now，软件开始更新；10下载完毕继续安装；11安装完毕停留在工作界面；12点第一个球形按钮，打开语言设置，将下拉箭头往下拉；13找到简体中文；14选择简体中文，就变成汉化版了，你看明白了吗？END经验内容仅供参考，如果您需解决具体问题(尤其法律、医学等领域)，建议您详细咨询相关领域专业人士。作者声明：本篇经验系本人依照真实经历原创，未经许可，谢绝转载。投票(39)已投票(39)有得(0)我有疑问(0)◆◆说说为什么给这篇经验投票吧！我为什么投票...你还可以输入500字◆◆非回享用户暂时不能发布经验“有得”&你还可以输入1000字◆◆如对这篇经验有疑问，可反馈给作者，经验作者会尽力为您解决！你还可以输入500字相关经验10210热门杂志第1期作文书写技巧886次分享第12期祝你好“孕”429次分享第1期当我们有了孩子321次分享第1期新学期 新气象142次分享第1期孕妇饮食指导503次分享◆请扫描分享到朋友圈Scratch能给我们带来什么--修改_百度文库
两大类热门资源免费畅读
续费一年阅读会员，立省24元！
Scratch能给我们带来什么--修改
上传于|0|0|暂无简介
阅读已结束，如果下载本文需要使用3下载券
想免费下载本文？
定制HR最喜欢的简历
下载文档到电脑，查找使用更方便
还剩1页未读，继续阅读
定制HR最喜欢的简历
你可能喜欢scratch硬件32+64位驱动程序下载__飞翔下载
单机游戏下载单机游戏下载基地
当前位置： →
→ scratch硬件32+64位驱动程序
scratch硬件32+64位驱动程序，压缩包包含scratch硬件驱动 32位和scratch硬件驱动 64位和CDM_2_06_00.exe。&安装说明根据自己的电脑情况，选择合适的安装文件，运行SETUP.EXE,点击INSTALL,等待安装完成即可。
安卓官方手机版
IOS官方手机版
scratch硬件32+64位驱动程序
本类软件分类
装机必备软件ESXi Hardware Requirements
ESXi Hardware Requirements
Make sure the host meets the minimum hardware configurations supported by ESXi 5.0.
Hardware and System Resources
To install and use ESXi 5.0, your
hardware and system resources must meet the following requirements:
Supported server platform. For a list of supported platforms, see the VMware Compatibility Guide at .
ESXi 5.0 will install and run only on servers with 64-bit x86 CPUs.
ESXi 5.0 requires a host machine with at least two cores.
ESXi 5.0 supports only LAHF and SAHF CPU instructions.
ESXi supports a broad range of x64 multicore processors. For a complete list of supported processors, see the VMware compatibility guide at .
ESXi requires a minimum of 2GB of physical RAM. VMware recommends 8GB of RAM to take full advantage of ESXi features and run virtual machines in typical production environments.
To support 64-bit virtual machines, support for hardware virtualization (Intel VT-x or AMD RVI) must be enabled on x64 CPUs.
One or more Gigabit or 10Gb Ethernet controllers. For a list of supported network adapter models, see the VMware Compatibility Guide at .
Any combination of one or more of the following controllers:
Basic SCSI controllers. Adaptec Ultra-160 or Ultra-320, LSI Logic Fusion-MPT, or most NCR/Symbios SCSI.
RAID controllers. Dell PERC (Adaptec RAID or LSI MegaRAID), HP Smart Array RAID, or IBM (Adaptec) ServeRAID controllers.
SCSI disk or a local, non-network, RAID LUN with unpartitioned space for the virtual machines.
For Serial ATA (SATA), a disk connected through supported SAS controllers or supported on-board SATA controllers. SATA disks will be considered remote,
not local. These disks will not be used as a scratch partition by default because they are seen as remote.
You cannot connect a SATA CD-ROM device to a virtual machine on an ESXi 5.0 host. To use the SATA CD-ROM device, you must use IDE emulation mode.
Storage Systems
ESXi 5.0 supports installing on and booting from the following storage systems:
SATA disk drives. SATA disk drives connected behind supported SAS controllers or supported on-board SATA controllers.
Supported SAS controllers include:
LSI1068E (LSISAS3442E)
LSI1068 (SAS 5)
IBM ServeRAID 8K SAS controller
Smart Array P400/256 controller
Dell PERC 5.0.1 controller
Supported on-board SATA include:
Intel ICH9
NVIDIA MCP55
ServerWorks HT1000
ESXi does not support using local, internal SATA drives on the host server to create VMFS datastores that are shared across multiple ESXi hosts.
Serial Attached SCSI (SAS) disk drives. Supported for installing ESXi 5.0 and for storing virtual machines on VMFS partitions.
Dedicated SAN disk on Fibre Channel or iSCSI
USB devices. Supported for installing ESXi 5.0. For a list of supported USB devices, see the VMware Compatibility Guide at .
ESXi Booting Requirements
vSphere 5.0 supports booting ESXi hosts from the Unified Extensible Firmware Interface (UEFI). With UEFI you can boot systems from hard drives, CD-ROM drives, or USB media. Network booting or provisioning with VMware Auto Deploy requires the legacy BIOS firmware and is not available with UEFI.
ESXi can boot from a disk larger than 2TB provided that the system firmware and the firmware on any add-in card that you are using support it. See the vendor documentation.
Changing the boot type from legacy BIOS to UEFI after you install ESXi 5.0 might cause the host to fail to boot. In this case, the host displays an error message similar to: Not a VMware boot bank. Changing the host boot type between legacy BIOS and UEFI is not supported after you install ESXi 5.0.
Storage Requirements for ESXi 5.0 Installation
Installing ESXi 5.0 requires a boot device that is a minimum of 1GB in size. When booting from a local disk or SAN/iSCSI LUN, a 5.2GB disk is required to allow for the creation of the VMFS volume and a 4GB scratch partition on the boot device.
If a smaller disk or LUN is used, the installer will attempt to allocate a scratch region on a separate local disk.
If a local disk cannot be found the scratch partition, /scratch, will be located on the ESXi host ramdisk, linked to /tmp/scratch.
You can reconfigure /scratch to use a separate disk or LUN.
For best performance and memory optimization, VMware recommends that you do not leave
/scratch on the ESXi host ramdisk.
To reconfigure /scratch, see .
Due to the I/O sensitivity of USB and SD devices the installer does not create a scratch partition on these devices.
As such, there is no tangible benefit to using large USB/SD devices as ESXi uses only the first 1GB.
When installing on USB or SD devices, the installer attempts to allocate a scratch region on an available local disk or datastore.
If no local disk or datastore is found, /scratch is placed on the ramdisk.
You should reconfigure /scratch to use a persistent datastore following the installation.
In Auto Deploy installations, the installer attempts to allocate a scratch region on an available local disk or datastore.
If no local disk or datastore is found /scratch is placed on ramdisk.
You should reconfigure /scratch to use a persistent datastore following the installation.
For environments that boot from a
SAN or use Auto Deploy, it is not necessary to allocate a separate LUN for each ESXi host.
You can co-locate the scratch regions for many ESXi hosts onto a single LUN.
The number of hosts assigned to any single LUN should be weighed against the LUN size and the I/O behavior of the virtual machines.}