Muvee AutoProducer ... Unlock The Feeling ... All-In-One
eBook: Leadership Secrets of the World’s Most Successful CEOs
Theme: Engelbert Humperdinck - Too Beautiful To Last
Includes:
01- Muvee AutoProducer v5.0.9.5 Build 856
02- Muvee ProModern Stylepack v2.0.0
03- Muvee ProClassic Stylepack v2.0.0
04- Muvee CoolStyles 2 Stylepack v5.0.0.3 Build 842
05- Muvee Kids Stylepack v5.0.0.3 Build 845
06- Muvee Hi-Octane Stylepack v5.0.6.4 Build 921
07- Muvee Soccer Style v5.0.0.9 Build 1000
Download: 263 MB
Part-1
Part-2
Part-3
Part-4
Part-5
Part-6: sfv file
Unrar password:
MUYF-TPachino
Muvee Technologies is the pioneer and leader in automatic video production. Its award-winning muvee autoProducer software lets anyone instantly transform dull video and pictures into professional-looking multimedia productions. Simply give muvee your video/pictures, add music, and pick a production style. In minutes, muvee intelligently selects the best scenes and automatically cuts them to the music with effects and transitions synchronized to the beat.
Styles are definitely autoProducer's secret sauce, providing variety and inventiveness that other products can't match. (PC Magazine)
Key Features:
For Video:
01- MagicMoments: Gives you more control over your video production. Pick your favorite shots! Discard those you dislike!
02- Tweak muvee: Allows you to make last minute changes. Replace video segment with another video segment you desire.
03- USB webcam & video capture: Supports DV/USB capture via Firewire and USB connections.
04- Any video formats: Supports a wide variety of video formats - MPEG1, MPEG2, WMV, AVI, DivX, MOV (Qucktime)
For Photos:
01- MagicSpot: Gives you more control on your photo transitions. Pick your sweet spot with magicSpot!
02- Tweak muvee: Allows you to make last minute changes. Replace a photo segment with another one you desire!.
03- Any photo formats: Supports a wide variety of photo formats - BMP, JPEG, GIF and TIFF.
More Cool Features:
01- Integrated DVD authoring: Make muvees and burn them into VCD, SVCD & DVD.
02- Blend music and soundtrack
03- Music formats: Supports popular music formats such as WAV, MP3, WMA and AAC audio.
04- Advanced Title & Credits
05- Make muvees with your mobile phone videos
and much more ...
2 comments:
USB Storage - FAQ for Driver and Hardware Developers
Updated: October 28, 2004
*
On This Page
Introduction Introduction
Windows Support and Usbstor.sys Windows Support and Usbstor.sys
Usbstor.sys and Device Class Support Usbstor.sys and Device Class Support
Usbstor.sys and "Designed for Windows" Logo Usbstor.sys and "Designed for Windows" Logo
Usbstor.sys and Power Management Usbstor.sys and Power Management
Call to Action and Resources Call to Action and Resources
The Microsoft Windows 2000 and Windows XP (and later) operating systems, as well as Windows Millennium Edition (Windows Me), contain native support for devices that comply with the Universal Serial Bus (USB) Mass Storage Class Specification. If the USB bus driver enumerates a mass-storage-class-compliant device on a computer running Windows, it will automatically load the USB storage port driver (usbstor.sys) for that device. This article provides answers to frequently asked questions from driver developers about usbstor.sys.
This paper is for developers who are new to developing USB Mass Storage Class devices that work with Windows operating systems.
Top of pageTop of page
Introduction
The Microsoft Windows 2000 and Windows XP operating systems, as well as Windows Millennium Edition (Windows Me), contain native support for devices that are compliant with the Universal Serial Bus (USB) Mass Storage Class Specification. If the USB bus driver enumerates a mass-storage-class-compliant device on a computer running Windows, it automatically loads the USB storage port driver (usbstor.sys) for that device.
This article provides answers to frequently asked questions from driver developers about usbstor.sys.
Additional documentation for usbstor.sys and driver support for USB mass storage devices are available in the current version of the Windows Driver Development Kit (DDK), available through the MSDN Library and from the Windows DDK Web site at http://www.microsoft.com/whdc/devtools/ddk/default.mspx.
Top of pageTop of page
Windows Support and Usbstor.sys
Q. What versions of the Windows operating system support USB storage using usbstor.sys as the storage port driver?
The following Windows operating systems provide native support for USB mass storage class devices:
•
Windows Server 2003
•
Windows XP
•
Windows 2000
•
Windows Me
USB mass storage class devices are supported by usbstor.sys, which is loaded using Plug and Play (PnP) hardware identifier (HWID) or compatible identifier matching in usbstor.inf.
Q. Do IHVs have to build their own USB storage support for Windows 98 Gold and Windows 98 Second Edition?
Yes. These earlier operating systems do not provide native USB storage support because the USB storage specification was not finalized during the development phase of these versions of Windows. For information and guidelines about developing USB storage support, see the USB storage sample driver in the Microsoft Knowledge Base Article Q257751 located at http://support.microsoft.com/default.aspx?scid=kb;en-us;Q257751
Note the following points:
If you are developing a composite device, you need to use USBD_CreateConfigurationRequestEx() in your vendor-specific USB storage driver. The function USBD_CreateConfigurationRequest() works correctly only for the first interface of a multiple-interface device. This issue has been addressed in the latest sample driver in the KB article Q257751.
Because Windows 98 and Windows 98 Second Edition (SE) have an issue related to the USB hub driver, use the URB_FUNCTION_SELECT_INTERFACE to work around the default 4 KB transfer limit when Usbhub.sys is loaded for the device as a composite parent driver, as described in this article.
If your device is a Bulk-Only device and you will never need to support a Control/Bulk/Interrupt (CBI) device, you can hard-code your vendor-specific storage driver to be Bulk-Only and remove the logic that decides which type of device it is. By doing this you can remove all of the CBI-specific routines to make the driver smaller. The latest sample in the KB article Q257751 has a #define called SUPPORT_CBI that helps to address this issue.
You must give your vendor-specific driver a unique, vendor-specific file name to avoid conflicts with other device vendors who also provide drivers based on this same sample code.
Note that the USB storage sample in KB article Q257751 now also supports composite devices. After you have developed a driver for your device, you should test it through the Windows Hardware Quality Labs (WHQL), to ensure compatibility with Windows.
Q: Can a USB storage device be the primary (and only) means of storage?
No. USB-based mass storage devices cannot be the primary hard disk storage solution on a regular system (Microsoft Windows Logo Program System and Device Requirements, B10.1.5.6). However, these devices might be expected to be a replacement for booting to load an operating system (for example using a CD-ROM drive over USB) on the primary boot drive or as a replacement for legacy floppy disk drives. Booting from an external USB CD-ROM or USB floppy disk drive requires BIOS support.
For more information and to review the latest WinHEC presentations for ideas see http://www.microsoft.com/whdc/device/storage/default.mspx.
Q: Can a host simultaneously have multiple, individual USB storage devices on a system?
Yes. A host can have multiple USB storage devices operational at the same time. Because the USB storage class uses bulk endpoints for transfers, having several storage devices operational at the same time might cause individual devices to scale back from peak throughput if there is bus congestion and if they are connected to the same host controller.
Q: Can a USB Mass Storage Interface have multiple alternative interfaces?
No. The USB Mass Storage Class Specification does not allow for alternate interfaces. If a device has an interface that complies with the USB Mass Storage Class Specification, it needs to be on the first interface setting (if the interface has more than one alternate interface setting) because (on current operating systems) usbstor.sys only looks at the first interface setting.
Q: Can a device have multiple logical units per target device?
The code in usbstor.sys does not make any assumptions about the number of logical units per target device. If it finds multiple logical units, the operating system enumerates each as a separate device. Refer to the KB articles Q324953 and Q316857 to find the Quick Fix Engineering (QFE) support for multiple logical units on Windows 2000. This QFE is also available in the Windows 2000 Service Pack 3 (SP3).
For more information about how multiple logical unit USB storage devices appear to the operating system, see the Windows XP Driver Development Kit.
Q: What problems and updates are known to affect storage solutions on earlier versions of the Windows operating system?
In Windows 2000 and Windows 98 SE a problem exists in Usbhub.sys, when it is loaded as the composite parent driver for a multiple-interface device. In such cases, during a _URB_SELECT_CONFIGURATION request, the child devices are configured with a 4-KB transfer limit on endpoints. To work around this problem, drivers for the child devices can issue a URB_FUNCTION_SELECT_INTERFACE request after the _URB_SELECT_CONFIGURATION request to override the default 4-KB transfer limit.
Windows Me. In Windows Me, Usbccgp.sys was developed to replace the composite parent driver functionality of Usbhub.sys. The usbccgp.sys driver does not have the default 4-KB transfer limit problem. However, a problem occurs with compatible IDs where the protocol byte field has a decimal notation instead of a hexadecimal notation.
A QFE is available to fix this issue in Windows 2000. Refer to KB article Q283787, titled "Multifunction USB Device Cannot Transfer 4 KB or Larger Files” for further information. This QFE is also available in Windows2000 Service Pack 3 (SP3). Contact your Microsoft Technical Account Manager (TAM) for additional information.
Q: Do customers running Windows XP or Windows 2000 need a new USB storage driver now that USB 2.0 is available?
No. Microsoft has provided a new miniport (usbehci.sys) driver and an updated usbport.sys and usbhub.sys driver to support USB 2.0 on Windows 2000 and Windows XP. For more details see http://www.microsoft.com/whdc/system/bus/USB/default.mspx. Client drivers (such as usbstor.sys) will continue to function on this new USB 2.0 stack.
In future versions of the Windows operating system, optimizations to the USB storage driver may be made to improve the performance of high-speed USB 2.0 devices.
Q: Does usbstor.sys need to be modified to support disks over 137 GB in size?
No. Support for disks that are larger than 137 GB is not an issue for the USB mass storage class driver. However, such support is an issue with the USB-ATA bridge chip in the external USB storage device.
USB-ATA bridge chip vendors are working on new devices that support the 48-bit ATA LBA mode. When these devices are available, the storage limit on a single device should be 2048 GB.
Q: Can usbstor.sys fail a query remove?
No. Usbstor.sys never fails a query remove. The failure comes from a higher level driver, or a filter driver. If you see such a failure, verify that you are not running any storage filter drivers.
Q: Can a vendor use SCSI pass through to talk to a USB storage device and send it vendor-specific commands?
IOCTL_SCSI_PASS_THROUGH or IOCTL_SCSI_PASS_THROUGH_DIRECT allow applications to send almost any SCSI command to a target device, with some restrictions. For additional details on the command and the restrictions, see http://msdn.microsoft.com/library/default.asp?url=/library/en-us/Storage_r/hh/Storage_r/k307_3ce0bb34-5f8d-40f8-ae98-24f597656ad0.xml.asp?frame=true in the latest Windows Driver Development Kit.
Top of pageTop of page
Usbstor.sys and Device Class Support
Q: Which device classes does usbstor.sys understand?
In Windows XP, Windows 2000, and Windows Me, usbstor.sys makes only one distinction:
bInterfaceSubClass == 06h
- OR -
bInterfaceSubClass != 06h
The value bInterfaceSubClass == 06h means that:
Command descriptor blocks (CDBs) should not be padded to 12 bytes.
Mode Sense / Mode Select commands should not be translated from 1AH / 15h to 5AH / 55h.
Subclass 0x06 should generally be used for flash memory devices.
The value bInterfaceSubClass != 06h means that:
CDBs should be padded to 12 bytes.
Mode Sense / Mode Select commands should be translated from 1AH / 15h to 5AH / 55h.
Q: Should IHVs use Bulk-Only or CBI for new USB storage devices?
Microsoft recommends the use of the Mass Storage Class Bulk-Only Transport (BOT) specification when developing new USB storage devices. A Bulk-Only Data Interface must include at least one bulk-in and one bulk-out endpoint. The Windows operating system chooses the first bulk-in and bulk-out endpoint for transactions. The reasons for the preference towards BOT are as follows:
•
Cheaper hardware: The Bulk-Only Transport specification requires fewer endpoints than the CBI specification. Fewer endpoints generally reduce overall hardware cost.
•
Compatible ID matching: Windows 2000, Windows Me, and Windows XP all have compatible ID support for ATAPI, FDD, and SCSI protocols over Bulk-Only Transport. Because of this, IHVs do not need to provide an information file (INF) containing their device’s hardware ID.
We highly recommend this scenario for flash storage devices.
Moving forward, innovation in Windows operating systems will revolve around the Bulk-Only Transport specification. There are currently no plans to include any new work to support new CBI devices.
Q: I am developing a new USB storage device but I want to load my OWN transport driver and NOT use usbstor.sys. What should I do?
Usbstor.sys is loaded on any interface that provides a class ID, subclass ID, or protocol ID that matches with a hardware ID or compatible ID in usbstor.inf.
To load a vendor-specific driver and NOT use usbstor.sys, do the following:
•
Set the class ID, subclass ID, or protocol ID on the interface descriptor to be vendor-specific.
•
Write your own INF and driver for the device. Include your device's hardware ID in your vendor INF and ensure that the hardware ID is not listed in usbstor.inf.
•
Test your driver with the latest Hardware Compatibility Test (HCT) to ensure device and driver stability. Note that you may NOT be able to use the standard WHQL storage tests and might have to test using the Universal Program.
Q: Does Windows currently support USB storage devices that use RBC protocol (that is, USB Storage Specification SubClass 0x01)?
Currently Windows 2000 or Windows XP do not provide support to handle USB storage devices that use the reduced block commands (RBC)(subclass 0x01) protocol. The issue with supporting RBC devices on Windows 2000 or Windows XP is that the Mode Sense commands are different, and the class drivers (DISK.SYS, CDROM.SYS, SFLOPPY.SYS, and CLASSPNP.SYS) do not understand the RBC version.
In addition, usbstor.inf does not have a compatible ID match for a USB RBC class device. Consequently, your USB storage device will not load usbstor.sys when you plug it in to a new Windows XP system. You will need to provide your own INF and drivers to support this device.
We do not recommend the use of RBC class devices for current Windows operating systems.
Q: What must I do to trigger Autorun on my USB storage device?
The Autorun capabilities are restricted to CD-ROM drives and fixed disk drives. If you need to make a USB storage device perform Autorun, the device must not be marked as a removable media device and the device must contain an Autorun.inf file and a startup application.
The removable media device setting is a flag contained within the SCSI Inquiry Data response to the SCSI Inquiry command. Bit 7 of byte 1 (indexed from 0) is the Removable Media Bit (RMB). A RMB set to zero indicates that the device is not a removable media device. A RMB of one indicates that the device is a removable media device. Drivers obtain this information by using the StorageDeviceProperty request.
For more information about the SCSI Inquiry command, see the T10 committee located at http://www.t10.org. This link leaves the Microsoft.com site
For more information about the StorageDeviceProperty, see the STORAGE_DEVICE_DESCRIPTOR storage structure in the Windows DDK, located at http://msdn.microsoft.com/library/default.asp?url=/library/en-us/storage_r/hh/storage_r/structs-general_3c393126-f5c8-47d8-bfb5-6127ce656e9a.xml.asp.
For more information on Autorun.inf files see the "Creating an AutoRun-Enabled Application" article located at http://msdn.microsoft.com/library/default.asp?url=/library/en-us/shellcc/platform/shell/programmersguide/shell_basics/shell_basics_extending/autorun/autoplay_works.asp?frame=true.
Q: Can Windows XP show a special icon for a drive in My Computer?
Device manufacturers can create personalized, or custom, product icons and include them in their driver packages so that the end user sees an icon that resembles the actual device when using Windows XP and future versions of the Windows operating system. These personalized icons are visible in the Autoplay window and in My Computer under Windows XP.
For complete details, see the article titled "Personalized Icons for Devices" located at http://www.microsoft.com/whdc/driver/install/devicons.mspx.
Top of pageTop of page
Usbstor.sys and "Designed for Windows" Logo
Q: Must a USB storage device contain a unique serial number?
Yes. To comply with the USB Mass Storage Class Bulk-Only Transport Specification, all USB storage devices must contain a unique (12 digits or longer) serial number, represented as a UNICODE string. Refer to section 4.1.1 of the USB Mass Storage Class (Bulk-Only Transport) specification and note that serial number characters must be 0x0030-0x0039 or 0x0041-0x0046.
A unique serial number on a USB device maintains the same device devnode as a user moves the device from USB port to port. This unique devnode ensures that properties (icons, policies, driver letters, and so on) associated with the device are not reset when the device is moved to a new port or when a second device with the same VID/PID/REV is added to the system.
IHVs must ensure that a device's serial number is unique in order for that device to comply with Windows operating systems (refer to Microsoft Windows Logo Program System and Device Requirements B2.6.3.1) and to pass WHQL certification. (HCT version 10.0, and later HCTs, will test the uniqueness of a serial number on any USB device if one is specified.)
Q: Where can I get a list of requirements for Windows operating systems and storage devices?
http://www.microsoft.com/whdc/winlogo/downloads.mspx for a list of requirements that removable storage devices need to comply with. Refer to the storage device requirements and USB bus/controller requirements in Microsoft Windows Logo Program System and Device Requirements.
Refer to the Windows XP DDK for additional details and requirements for USB storage devices in order to be compatible with usbstor.sys.
Q: What WHQL tests must an IHV run on a USB storage device to receive the "Designed for Windows" logo for Windows XP?
Details are available at http://www.microsoft.com/whdc/whql/default.mspx. If you have additional questions, locate your device class on the WHQL Support page located at http://www.microsoft.com/whdc/whql/resources/support.mspx and send your question to the appropriate support alias.
Top of pageTop of page
Usbstor.sys and Power Management
Q: I want to embed a storage device inside a laptop, but still want to conserve power. What should I consider in this design?
Windows XP supports selective suspension of USB devices, as described in "Selective Suspension of USB Devices" in the "USB Design Guide" section of the current Windows DDK. The Selective Suspend feature allows a driver to turn off the USB device it controls when the device becomes idle, even while the system itself remains in a fully operational power state (S0). This feature is primarily intended to conserve battery power in laptops.
The Selective Suspend feature allows drivers to idle the host controller, any empty USB hubs including the Root Hub, and the full range of USB devices supported by the operating system. Windows XP does not natively support Selective Suspend in usbstor.sys. This is being investigated for future operating system releases and will require changes in:
•
The USB Mass Storage Class Specification
•
The USB storage hardware (to support remote wake functionality)
•
The USB storage driver in Windows
Alternatively, if you design your storage solution as a compound device and place the bridge chip behind a USB hub, you can then emulate device removal upon media removal. Windows XP will interpret the emulation to understand that the storage device has been removed from the USB hub. An empty hub will then be selectively suspended by the Windows XP USB stack.
For your implementation of this solution to work properly, the compound device’s hub must not be more than one hub away from the root hub. Although this solution might reduce power consumption, it will also make the USB storage device disappear from Device Manager and My Computer.
Operating system support for selective suspension of USB storage devices (rather than only compound devices) is planned for a future release of the Windows operating system.
Q: Should my USB device set the remote wake bit on the USB storage device's configuration descriptor?
The Windows USB storage driver does not currently use the remote wake field of the device. This will change, however, if USB storage devices intend to use selective suspend capabilities in future versions of the Windows operating system.
The WHQL HCT 10.0 kit also validates the use of the remote wake bit. If the remote wake bit is set, the IHV has to prove to WHQL that this bit does in fact wake the system.
Q: Did the removal policies for USB storage devices change in Windows XP?
Customer feedback showed that consumers were unplugging USB storage devices from systems, without going to the "safely remove hardware" tab in the system tray on Windows 2000 systems. Such random removal sometimes left storage devices in a corrupted state.
To mitigate the likelihood of data loss in surprise removal scenarios, Windows XP refined the caching policy for removable storage. As of Windows XP Beta 2, for consumer-oriented removable storage (USB, Flash, Zip, and so on), write caching is disabled by default.
Disabling write caching means that, instead of saving up changes for a file on a removable storage device and then doing a bulk write, Windows XP writes changes to the file as the changes are made. This keeps data on removable storage devices more current, mitigating the likelihood of data loss. However, disabling write caching also has a performance impact.
To view removable properties associated with a USB storage device, open Device Manager, select the storage device's properties, and see the Policies tab.
For additional details on removal policies, refer to http://www.microsoft.com/whdc/system/pnppwr/hotadd/XPrem-devs.mspx.
Top of pageTop of page
Call to Action and Resources
Call to Action:
•
Device manufacturers for USB mass storage devices must review this entire FAQ list. If your question is unanswered, contact usbstor@microsoft.com.
•
Device manufacturers for USB mass storage devices must include a USB serial number in their USB Bulk-Only device.
•
Device manufacturers should arrange to send newer models of their USB bridge chips to the Windows team for testing.
•
For related information, please visit: http://www.microsoft.com/whdc/default.mspx.
Hello, Everybody. I have succeeded installing Windows XP SP2 into my IBM x31 Notebook.
I will take a brief on how I do that. ;-)
because my notebook without a dock, and I didn't have a USB cdrom, neither a usb floppy
disk. so i have to use VMware to help me make the USB disk bootable.
I follow the link below to modify the files.:
http://www.ngine.de/index.jsp?pageid=4176
1. I partition my 40G USB hardisk as 20G/20G, both at fat32 format. using XP's storage manager tool,
(I didn't use the HP usb disk format tool)
and then mount it under VMware (means that vmware will use it as raw disk.),
make a dos system on the first partition. (boot the VMware by DOS IMG floopy image,
and just execute sys a: c:, then also copy necessery files. such as HIMEM.SYS and SMARTDRV.EXE)
and then you can boot the VMware system with this disk.
2. close VMware, and copy the whole I386 to the USB disk first partition.
3. reboot my notebook, start the real installation. unfortunately, I cannot pull my internal harddisk
out of the notebook, so I start the setup while the internal harddisk still here.
4. nothing strange, just as normal XP setup. it took about 1 hour. longer then normal setup.
it works, just so simple!
btw: I didn't change the boot order in BIOS. just when boot, press F12, select USB harddisk
as the boot disk.
cheers!
Iceman_jkh
Post a Comment