M2V to ISO Automation

Hi All,
I am hoping to find a way to automate a DVD workflow.
I have looked into Rimage and this will take an ISO and burn/label as many physical copies as you would like.
The only hole now is finding a solution for getting from an M2V file created from a transcoding software to an ISO. I am just curious if anyone knows of any scripts that can do this? If so, I could render out to a watch folder that the automated program can watch for...
The menu for the DVD would need to have a background that can be predetermined as well as a button to click to play that would be titled the same as the M2V file.
If anyone has any experience with anythign of the like I would love to hear about it!
Thanks in advance,
Jesse Korosi
www.jessekorosi.com

There has to be some type of Apple Script or something of the like that could do this...?

Similar Messages

Automator to mount multiple ISO files on external USB drives

I have several ISO files on an external USB drive on a Mac mini. Double clicking on any of the ISO mounts it, one at a time.
I need to have an automator that mounts ALL ISO it can see on a given USB external drive. I have written an Apple script but that hangs up the Mac mini. I need help because I am not familiar with Applescript or Apple automator. I used Unix years ago, butg have a hard time with AppleScript.

Macs can't normally write to NTFS drives:
http://discussions.apple.com/click.jspa?searchID=7426620&messageID=4582486
Your other problem sounds like another computer has the files open or application has the files open simultaneously. Try shutting down your Mac, and isolating your Mac from any network and try rebooting again in safe mode by holding the shift key at startup.

WinPE 4.0 automated ISO deploy.

Hi Guys,
I'm currently working on a project and I'm trying to create a PE image that boots and applys an image inside of the .wim . I have the folder setup, .swm files inside of a folder along with a script that boots into a format and then apply-image of source
files I provided. In testing this, I am immediately presented with an error - unable to create ramdisk. The image I'm trying to apply is fairly large, about 11gigs. I upped the scratchspace on the wim thinking that would help, but even
configured at 512mb it still errors out. I don't even get into the PE environment. Any ideas on what I'm doing wrong or if there's a better way for me to approach this? I just need a bootable ISO that will prompt to apply and then apply the
image I have embedded in the boot.wim file. Any help is appreciated. Thanks!
Ryan

Hi,
This is caused by a driver bug check during boot. Make sure all drivers have been updated. I would suggest you to update all device drivers and check.
Also, please help to confirm following questions:
1. what's the pre-OS on the computer you would like to deploy?
2. Did you mean you get the 11GB wim split into several swm file? what's the main part of your script to deploy the image?
Please see that in this article it mentioned that Windows 8/8.1, the setup is not supported to install swm file.
Split a Windows Image (.swm) File to Span Across Multiple DVDs
http://technet.microsoft.com/en-us/library/hh825096.aspx
Please let me know more detailed information about what you have done and would like to do during this project, I will take some time to test the results.
Kate Li
TechNet Community Support

Checksum for windows.ISO created by MS mediacreationtool.exe

Primary question - What is the sha1 {&/or Md5} checksum for the "windows.ISO" file downloaded when using the MS supplied "mediacreationtools.exe"? I specifically want the checksum for the ISO resulting from selecting
Language: English {UK} Edition: Windows 8.1 Architecture: 64-bit {x64}
Situation - I am wanting to do a clean install of win 8.1 {build9600} onto a laptop which has a barely usable build 9600 already installed, damaged recovery partitions, and no OEM recovery media.
I have downloaded and used the Microsoft supplied tool 'mediacreationtool.exe' which subsequently downloads a file called 'Windows.iso'. I wish to verify the integrity of that ISO file to ensure it arrived correctly. Obviously I want to do that
**before** I repartition the HD and attempt to re-install OS rather than simply cross my fingers and hope all goes well.
I have searched for a checksum or other method to ensure the ISO is 'good' yet could not find one.
I downloaded a second copy of the same type of ISO using the same method with the same tool. I had hoped for the same checksum on both ISOs as a means of verification.
If the 'media creation tool' uses an 'automatic' checksumming/correction as part of the download process to ensure the integrity of the downloaded ISO then it appears to be untrustworthy given that the two ISOs it gave me, which should have
been the same, unfortunately arrived with different checksums.
It is obviously ludicrous to continue downloading >3GB files until I find a pair whose checksum match. I am frustrated by this situation.
I presume Microsoftland employs at least a few brainiacs who are capable of understanding what checksums are and how they can be useful. Consequently I am astounded that MS does not publish the checksums for ISOs officially obtained from MS, using
an official MS tool. Can anyone shed some light on why this situation exists and offer a useful remedy?

Thankyou Shaon for your continued attention and help.
I had ignorantly presumed the MCTool was in effect a download manager which downloaded/checked the entire ISO rather than 'constructed' it. Your advice that it is not possible to gain a common checksum of any ISO created by the tool obviously answers
my primary question.
Yet the intent behind that initial question was to gain an understanding of how I can verify the integrity of the install media, downloaded using official MS method, which I intend to use as the basis for building the winOS. In this respect I am
hardly any closer to my goal of being able to verify/trust the media to perform a "clean install".
I mean "clean" in both senses of the word. The concept of SISO pre-dates Microsoft. The fact that the ISO doesn't contain enough s##t to stop it booting, or even setting up an OS, does not prove that the ISO or the OS constructed from
it does not in fact contain s##t which might unduly complicate processes down the line.
My enquiry is not merely an academic one.
I have been asked to fix an Acer laptop for a boy who for a few short months proudly enjoyed his new rig. The laptop came with win 8.0 pre-installed and all the devices worked as expected. He was a good boy and followed recommended procedure by
allowing automatic updates.
MS effectively coerced this kid into "upgrading" to build 9600 when they unexpectedly removed support for full updates on the breed of OS he was using. MS deceived him into readily accepting the installation of "windows 8.1 update
1" by strongly implying that it was, well... you can read, merely an "update" - not even big enough for an 8.2 moniker.
"Win 9" broke the kid's heart. He was suddenly the kid with the gimpy computer - no webcam, a wild trackpad and a schizophrenic network connection. Whilst still under warranty, Acer performed their magic and "clean installed"
build 9600, leaving the win8.0 recovery and original 'push button' partitions in place. This gave the boy an impressive 6 partitions but didn't actually fix any of his problems.
Acer then abandoned this kid by gutlessly feeding him 'professional scareware', blaming all his woes on malware. The frustrated boy, aided by well-meaning friends, over-reacted to this supposed threat and further trashed his system {as indication
- a year later I found it running two active AVs along with services for an extra two}.
Laughed at by his macbook using brother, the boy abandoned his MicroSelfish rig.
The pity about this whole saga is that even when half-broken Win 9 looks like it's actually a decent OS. If only it could simply be instructed to play nicely with devices.
I have found countless sad accounts of systems which, after 'updating' to build 9600, have exhibited strikingly similar problems to those which exist on the machine I am working with.
I find it interesting to note that there are comparatively few accounts of troubles after a "clean install". It isn't clear to me whether this is a result of people having abandoned their machines like the kid did or whether they simply
reverted back to builds 9200 or 9400 {"stuff the updates"}.
I suspect lots of people paid 'Danegeld' for either a new build 9600 install disk or a magic fix from a professional who had such a disk and performed a clean install.
I also suspect there were many who couldn't afford to pay and were subsequently {and ironically} encouraged by MS's actions to download the media from 'unofficial' sources. I now wonder if I should attempt to do the same - at least I could easily
verify the media with an officially published checksum and move on.
Microsoft eventually provided a tool which {it is claimed} can be used to facilitate a "clean install" of build 9600. I have used this official tool to download the setup media.
I do not have the option of reverting back to the originally installed {and no longer supported} 'build 9200'. Those partitions were damaged. The existing build 9600 was also badly damaged.
I have tested {OS independent} the major hardware components and am convinced the problems are all software related. I feel that doing a clean install of the OS and replacing a couple of wonky drivers would go a very long way towards resolving
all issues.
I anticipate that finding and testing the correct drivers may be a time consuming task yet the process should nonetheless be relatively straightforward.
I want to use "known good" media to establish a "known good" baseline for the OS before applying updates, drivers, and {lastly} other software. I am astounded that the seemingly simple task of verifying I am starting this process
with "known good" media with "known good" content has be so difficult.
I wonder why MS insists on a "near enough is good enough"/"suck it and see"/"cross your fingers"/"have some faith" approach by it's customers. Does MS management operate this way?
I am not encouraged by either the process or the behaviours of the MS supplied MCTool. The first ISO it 'constructed' for me will not even boot. I have twice burned it to dvd and tested. The MCTool gave me no indication whatsoever that it had failed
to construct the ISO correctly.
The second ISO it constructed for me does boot up and does install an OS. I have now used that install media multiple times to build the OS foundation. All installations have been unexpectedly problematic. To put this into context, I *did* expect
there to be problems with the operation of some devices.
When allowed, the OS self-activates using the BIOS-embedded key.
I have tried to inject 3rd party drivers before MS OOB ones. This did not fix any issues. It may simply be that I need to keep searching for the "correct" drivers {there appears to be a bewildering amount of choices}.
Looking through WUC I have gained the impression that MS has now taken the lead in providing hardware drivers {esp. when compared to the embarrassing filth which Acer calls "Support"}. So I decided to trust in the fully automated MS update
process to see if these updates can eventually lead to MS supplied drivers which *actually* work.
Frustratingly, most of the updates "failed". I have tried to apply these updates with and without Defender running. I have repeatedly used the MS 'fixit' tool which keeps telling me it has found and "fixed" problems. Very ugly.
I now wonder how I might, with a straight face, eventually advise the boy to keep his "win9" OS fully updated using the officially recommended method.
The machine is not ancient - manufactured in mid-2013.
Basic OOB MS drivers for webcam and touchpad work. Whilst I have not yet extensively searched for alternatives drivers for these devices, the OEM supplied drivers and software I have tried break them again. It may be that basic drivers will
be the best that computer geeks can offer the boy and that he will have to find other uses for his multi-finger gestures.
Regarding the frequent network dropouts I have searched for and {conservatively} applied a variety of "fixes" for alarmingly similar problems which I have found splashed all over the internet. I have used things like ipconfig/netsh commands,
changing DNS, switching off power management for the network devices, etc. None have lasting effect.
Throughout, I have tried to avoid introducing any major 3rd party software which might complicate investigations yet I was forced to install an alternate browser after IE {which I haven't used since IE3} absolutely refused to save web pages in
any format {incl. text}. Apart from suffering the same network connection issues, the alternate browser appears to work just fine.
This is 2015. "Win8.1 update 1" was introduced a reasonably long time ago. I am sick to death of having to do all this monkeying around to properly install MS's current OS and have it play nicely with the devices on the underlying machine.
I am especially peeved that I don't even know if any of the issues I face whilst trying to resolve the matter simply stem from flawed files on the install media. Even on the damaged OS I originally found on the machine IE and auto updates worked
fine.
This is fundamentally an issue of 'trust'.
At this stage of the game the peaceful win7 on my desktop machine will *never* be ugraded to another Microsoft OS. I would also throw this POS Acer/win9 away if I could also gutlessly ignore the boy who has already been shafted by big men in suits.
So I seek your further help, on behalf of the boy.
I do *not* here and now seek help with all the problems which exist on the machine. I particularly seek help regarding how to verify the integrity of the media used to install the OS.
I have no idea how the size of "install.esd" relates to determining the integrity of the hundreds of other files which also populate the ISO. Nonetheless I checked this within both ISOs I received {one now "known bad"} and both
matched yours for size. This method appears to prove nothing.
I don't seek clarity about the above process and will simply presume it was worth a try anyway. It did however lead me to another line of enquiry which may prove useful {Yet may prove to be wishful thinking founded on ignorance}.
Rather than comparing filesize, wouldn't it have been more exact to compare checksums for the file? Further, couldn't this entire issue of verification be solved by extracting all the files from their ISO container, checksumming the resulting individual
files, then comparing checksums?
{as a random example, I presume that "/boot/resources/bootres.dll" *is* v6.3.9600.16384 *is* "17.8KB" in size *is* datestamped "Thursday, 22 August 2013, 10:39:14 PM" *is* sha1 "3e8c4c5dcc9797f596dcca7334f405b217242190"
-- every day of the week, everywhere in the world., within any of the same 'type' of ISOs created by MCTool.}
Although the above method is more cumbersome than simply comparing the checksum for one file {ie the ISO} it would still be a relatively simple thing to do programmatically with regularly available tools - 7-zip/ISObuster etc to extract the
files, any of a number of tools/methods to gain an ordered list of checksums plus a tool capable of showing differences between two lists of checksums {eg. winmerge}.
By doing a simple comparison, any individual with an MS supplied ISO/disk could essentially verify the integrity of the contents {ie the parts if not the whole}. Obviously, this would involve having a reliable list to compare against.
I suppose MS could officially provide this data, even in a simple text file. Do you know if they have? {I can't see one within the ISO itself which would seem to be a logical place for it}.
If MS has not provided this data then perhaps the MS community could independently establish such lists. It wouldn't take very many comparisons before a reliable list could be published. Perhaps such lists already exist?
At a pinch, it seems to be that any two customers possessing what is ostensibly the same ISO to produced the same type of OS might alone be able to establish confidence in the *contents* of their ISOs if they compared the checksums of the extracted
files and they exactly matched.
Obviously, if the checksums of any of the compared files do not match then the data set is too small to establish which copy of a non-matching file, if either, is true.
Is the above reasoning and strategy sound?
Otherwise is there an alternative workaround?
Or are Microsoft customers best served by firing up a bittorrent program and trying their luck?

Problem in unattended installation of Windows 10 OS image from its ISO

Hi There,
I am trying to install unattended Windows 10 OS image from its ISO by unattended.xml. While doing it windows boot screen get stuck at windows setup screen where it ask input for Language, TIme format and Keyboard input method. For same
process if I use windows 8.1 ISO for installation it works fine. From technet I come to know that Windows 10 has NT DISM version as 6.4 and 8.1 has 6.3. But I am not getting how I can make these change in my automation..
We are creating a FLP file which includes (unattended.xml and few other files)and then specify that file to Vmware workstation Windows 10 image floppy drive and Windows 10 iso to DVD drive and then booting the VM.
Same process works for Windows 8.1 OS unattended installation but it is getting failed for Windows 10.
Please help.
Regards,
Nortonboy

Hi Alex,
I am using ISO :- 9841.0.140912-1613.FBL_RELEASE_CLIENTPRO-CORE_OEMRET_X64FRE_EN-US.ISO
Answer file :- autounattend.xml.
Yeah same answer file works for Win 8.1 but when I am useing above ISO which is same what you mentioned but still it stuck.
I am using below content in autounattend.xml
##################################3
<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">
<settings pass="windowsPE">
<component name="Microsoft-Windows-International-Core-WinPE" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" processorArchitecture="amd64">
<SetupUILanguage>
<UILanguage>en-us</UILanguage>
</SetupUILanguage>
<InputLocale>en-us</InputLocale>
<SystemLocale>en-us</SystemLocale>
<UILanguage>en-us</UILanguage>
<UserLocale>en-us</UserLocale>
</component>
<component name="Microsoft-Windows-Security-SPP-UX" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SkipAutoActivation>true</SkipAutoActivation>
</component
<component name="Microsoft-Windows-Setup" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" processorArchitecture="amd64">
<UserData>
<AcceptEula>true</AcceptEula>
<ProductKey>
<WillShowUI>OnError</WillShowUI>
<Key></Key>
</ProductKey>
</UserData>
<Display>
<ColorDepth>32</ColorDepth>
<HorizontalResolution>1024</HorizontalResolution>
<VerticalResolution>768</VerticalResolution>
</Display>
<ComplianceCheck>
<DisplayReport>OnError</DisplayReport>
</ComplianceCheck>
<DiskConfiguration>
<WillShowUI>OnError</WillShowUI>
<DisableEncryptedDiskProvisioning>true</DisableEncryptedDiskProvisioning>
<Disk>
<DiskID>0</DiskID>
<WillWipeDisk>true</WillWipeDisk>
<CreatePartitions>
<CreatePartition>
<Extend>true</Extend>
<Order>1</Order>
<Type>Primary</Type>
</CreatePartition>
</CreatePartitions>
<ModifyPartitions>
<ModifyPartition>
<Active>true</Active>
<Format>NTFS</Format>
<Label>Windows</Label>
<Order>1</Order>
<PartitionID>1</PartitionID>
</ModifyPartition>
</ModifyPartitions>
</Disk>
</DiskConfiguration>
<ImageInstall>
<OSImage>
<InstallTo>
<DiskID>0</DiskID>
<PartitionID>1</PartitionID>
</InstallTo>
<WillShowUI>OnError</WillShowUI>
<InstallToAvailablePartition>false</InstallToAvailablePartition>
</OSImage>
</ImageInstall>
</component>
</settings>
<settings pass="specialize">
<component name="Microsoft-Windows-Security-SPP-UX" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" processorArchitecture="amd64">
<SkipAutoActivation>true</SkipAutoActivation>
</component>
<component name="Microsoft-Windows-LUA-Settings" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" processorArchitecture="amd64">
<EnableLUA>false</EnableLUA>
</component>
<component name="Security-Malware-Windows-Defender" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" processorArchitecture="amd64">
<DisableAntiSpyware>true</DisableAntiSpyware>
</component>
<component name="Microsoft-Windows-SystemRestore-Main" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" processorArchitecture="amd64">
<DisableSR>1</DisableSR>
</component>
<component name="Microsoft-Windows-SQMAPI" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" processorArchitecture="amd64">
<CEIPEnabled>0</CEIPEnabled>
</component>
<component name="Networking-MPSSVC-Svc" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" processorArchitecture="amd64">
<DomainProfile_EnableFirewall>false</DomainProfile_EnableFirewall>
<PrivateProfile_EnableFirewall>false</PrivateProfile_EnableFirewall>
<PublicProfile_EnableFirewall>false</PublicProfile_EnableFirewall>
<DomainProfile_DisableNotifications>true</DomainProfile_DisableNotifications>
<PrivateProfile_DisableNotifications>true</PrivateProfile_DisableNotifications>
<PublicProfile_DisableNotifications>true</PublicProfile_DisableNotifications>
</component>
<component name="Microsoft-Windows-Shell-Setup" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" processorArchitecture="amd64">
<UserAccounts>
<AdministratorPassword>
<Value>password</Value>
<PlainText>true</PlainText>
</AdministratorPassword>
<LocalAccounts>
<LocalAccount wcm:action="add">
<Password>
<Value>symantec</Value>
<PlainText>true</PlainText>
</Password>
<Description>Automation Account</Description>
<DisplayName>Automation Account</DisplayName>
<Group>Administrators;Power Users</Group>
<Name>Automation</Name>
</LocalAccount>
</LocalAccounts>
</UserAccounts>
<OOBE>
<HideEULAPage>true</HideEULAPage>
<HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
<ProtectYourPC>3</ProtectYourPC>
<NetworkLocation>Other</NetworkLocation>
</OOBE>
<Display>
<ColorDepth>32</ColorDepth>
<HorizontalResolution>1024</HorizontalResolution>
<VerticalResolution>768</VerticalResolution>
</Display>
<TimeZone>Pacific Standard Time</TimeZone>
</component>
<component name="Microsoft-Windows-International-Core" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" processorArchitecture="amd64">
<InputLocale>en-US</InputLocale>
<SystemLocale>en-US</SystemLocale>
<UILanguage>en-US</UILanguage>
<UserLocale>en-US</UserLocale>
</component>
</settings>
</unattend>
Do you guys have any inputs on this issue
Nortonboy

Senior Test Automation Engineer LabView Perm Position in San Diego

Senior Hardware Test Automation Engineer- LabView
Company is, headquartered in San Diego, California, is focused on developing technology for the continuous monitoring of glucose in people with diabetes. Company is committed to developing technologies and products that improve the lives of people with diabetes and is currently looking for a Senior Test Automation Engineer.
Summary
This position is ideal for a highly self-motivated individual with software and hardware skills to strategize and design custom tools and test automation to meet design, cost and delivery targets.
As a Senior Test Automation Engineer, you’ll be bridging R&D to volume production by creating functional tests using LabView for production of Company products.
Duties & Responsibilities:
Create automated processes and test systems. Transition new products from prototype to production. Participate in design reviews. Develop test plans. Develop test software and hardware platforms. Review designs for manufacturability, improving cost & quality and increasing yields. Programming in high-level languages or scripting languages to control T&M Instruments and electromechanical systems. Program motion control and data acquisition systems. Develop test strategies to drive test time reduction. Develop test requirements and procedures in concurrence with design requirements. Document test procedures and results in conformance with ISO and FDA standards.
Required Qualifications:
Bachelors or Masters Degree in Electrical Engineering or similar discipline. At least 7 years experience in test automation, expert level designing and developing with LabView. Experience with relational databases. Experience with C#. Solid technical and theoretical background of electronics hardware and software. Demonstrated ability to work effectively in a fast-paced, team oriented, multi-tasking environment and to be willing to do what it takes to meet project commitments and deadlines. Good interpersonal skills, including good technical communication skills, must be self-directed, self-motivated and be able to work in a cross-functional team environment. Ability to work in a highly dynamic environment. Advanced knowledge in setting up ATE test suite running on LabVIEW. Experience leading projects and also interfacing with engineering, suppliers and contract manufacturer. Experience in RF is highly desirable. Advanced software-programming skills. Experience in statistical data analysis tools. PCB in-circuit and functional test knowledge is an asset. Experience in all facets of qualification, including environmental, HALT, and ESD testing would be an asset.
Please send resume to: [email protected]: 951-303-1841. Company offers an excellent benefits package and great work environment.
Retained Search Firm specializing in TElecom, Medical Devices, Biomed, BioTech, Ate, Semi, Legal, Medical, Real Estate, Commercial Real Estate, IT

Hi
I completed my M.S in electronics engineering and working with GE in INDIA since June 2005. I have total 2 years of experience with LabVIEW and have the follwoing skills.
Intermediate-to-advanced knowledge of LabVIEW.
Familiarity with data acquisition concepts and hardware.
Ability to troubleshoot electrical and electronic systems at the module and equipment level.
Discipline and organization with respect to software maintenance and version management.
Ability to work both alone and with colleagues to solve problems and to weigh the merits of differing approaches
you can reach me at [email protected]
Please find attached resume.
Thanks & Regards
Anil Punnam
Attachments:
Resume_Anil.pdf ‏1 KB

=?iso-8859-1?Q?Re:_=28PS=29_Im=E1genes_de_Rango_din=E1mico_HDR_-3?=

This is a multi-part message in MIME format.
------=_NextPart_000_004C_01C816E0.3950EF70
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sin =E1nimo de ofender pero creo que Juan deber=EDas
sustituir a Andres =
Cayon en cuanto al coordinador de Macromedia.. colabora menos
que tu, no =
tiene pedazo art=EDculos como estos.
"Juan Muro" <[email protected]> escribi=F3 en el
mensaje =
news:[email protected]...
---> viene del anterior
Pues bien, ya estamos listos para hacer nuestra primera
im=E1gen HDR, =
tenemos la c=E1mara, el tr=EDpode y el disparador
autom=E1tico y =
adem=E1s ya sabemos c=F3mo ajustamos el diafragma de manera
manual, o =
bien hemos comprobado que nuestra c=E1mara dispone del
maravilloso =
mecanismo de disparo bracketing, (y si esto es cierto quiero
aclarar =
que debemos probar las diferentes aperturas del diafragma
antes de =
disparar en bracketing, pues este modo de disparo
autom=E1tico no ajusta =
la velocidad de obturaci=F3n respecto a la apertura del
diafragma y por =
=E9so nos puede variar la profundidad de campo de tal manera
que nos =
encontramos con zonas m=E1s borrosas que otras dependiendo de
su =
distancia al objetivo, lo cual debemos evitar pues las fotos
que =
obtengamos para componer luego la im=E1gen HDR deben ser
absolutamente =
iguales salvo en la luz).
Pero claro si nos hace falta un tr=EDpode y al menos dos o
tres fotos, =
nunca podremos conseguir una foto HDR en movimiento. Pues no,
no es =
cierto, podemos hacerla, pero simul=E1ndo el HDR a partir de
una buena =
captura RAW, como dije en el primer mensaje, =E9so veremos
despu=E9s =
c=F3mo se hace.
De momento lo importante es conseguir las tomas que
comprondr=E1n =
nuestra imagen final. Lo primero ser=E1 ajustar la
sensibilidad ISO de =
la pel=EDcula a la menor posible (a la que corresponda,
habitualmente a =
21 DIN -- 100 ISO para exteriores normalmente iluminados),
as=ED =
evitaremos el ruido =F3ptico. Lo segundo es ensayar el
m=E9todo de =
apertura del diafragma sin que se nos mueva ni un =E1pice la
c=E1mara. Y =
lo tercero es hacer las fotos, cuantas m=E1s mejor, con un
m=EDnimo de =
dos fotos podemos obtener ya un hdr, pero lo normal es
hacerlo con tres, =
aunque yo he llegado a hacer hasta siete tomas diferentes de
la misma =
im=E1gen.
En estas tomas no tenemos la necesidad de valorar el
contraluz, ni por =
tanto la posici=F3n del sol respecto de la c=E1mara, ni si
alg=FAnas =
partes de la im=E1gen quedar=E1n solarizadas, ni siquiera si
existe =
alg=FAn objeto entre el foco luminoso y el objetivo, porque
todos estos =
obst=E1culos habituales quedar=E1n superados con esta
t=E9cnica.
Pero s=ED debemos valorar el tiempo de exposici=F3n, o lo
que es lo =
mismo la velocidad de obturaci=F3n del diafragma, porque de
ella depende =
en gran medida la cantidad de luz que recibe nuestra im=E1gen
y la =
definici=F3n de las texturas que contiene.
Luego guardaremos las im=E1genes en formato Tiff o Psd y las
=
volcaremos a nuestra computadora, donde las podemos renombrar
(aunque no =
es estrictamente necesario, pero ayuda para organizarse).
Lo dem=E1s ser=E1 todo hecho con nuestro viejo conocido
Photoshop, =
aunque solo admiten esta t=E9cnica las versiones CS2 y CS3, =
b=E1sicamente porque antes no se hab=EDa inventado, je, je.
---> contin=FAa
------=_NextPart_000_004C_01C816E0.3950EF70
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0
Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.3199"
name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Sin =E1nimo de
ofender pero creo que =
Juan deber=EDas=20
sustituir a Andres Cayon en cuanto al coordinador de
Macromedia.. =
colabora menos=20
que tu, no tiene pedazo art=EDculos como
estos.</FONT></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT:
5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"Juan Muro" <<A=20
href=3D"mailto:[email protected]">[email protected]</A>>
=
escribi=F3 en el=20
mensaje <A=20
=
href=3D"news:[email protected]">news:fff5hs$se2$1@forums=
.macromedia.com</A>...</DIV>
<DIV><FONT face=3DArial
size=3D2><EM>---> viene del =
anterior</EM></FONT></DIV>
<DIV><EM><FONT face=3DArial
size=3D2></FONT></EM> </DIV>
<DIV><FONT face=3DArial size=3D2>Pues bien, ya
estamos listos para =
hacer nuestra=20
primera im=E1gen HDR, tenemos la c=E1mara, el tr=EDpode y el
=
disparador autom=E1tico y=20
adem=E1s ya sabemos c=F3mo ajustamos el diafragma de manera
manual, o =
bien hemos=20
comprobado que nuestra c=E1mara dispone del maravilloso
mecanismo de =
disparo<EM>=20
bracketing, </EM>(y si esto es cierto quiero
aclarar que debemos =
probar=20
las diferentes aperturas del diafragma antes de disparar en
=
bracketing, pues=20
este modo de disparo autom=E1tico no ajusta la velocidad de
=
obturaci=F3n respecto=20
a la apertura del diafragma y por =E9so nos puede variar la
=
profundidad de campo=20
de tal manera que nos encontramos con zonas m=E1s borrosas
que otras =
dependiendo=20
de su distancia al objetivo, lo cual debemos evitar pues las
fotos que =
obtengamos para componer luego la im=E1gen HDR deben ser
absolutamente =
iguales=20
salvo en la luz).</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Pero claro si
nos hace falta un =
tr=EDpode y al=20
menos dos o tres fotos, nunca podremos conseguir una foto
HDR en =
movimiento.=20
Pues no, no es cierto, podemos hacerla, pero simul=E1ndo el
HDR a =
partir de=20
una buena captura RAW, como dije en el primer
mensaje, =E9so =
veremos =20
despu=E9s c=F3mo se hace.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>De momento lo
importante es conseguir =
las tomas=20
que comprondr=E1n nuestra imagen final. Lo primero ser=E1 =
ajustar la=20
sensibilidad ISO de la pel=EDcula a la menor
posible (a la que=20
corresponda, habitualmente a 21 DIN -- 100 ISO para
exteriores =
normalmente=20
iluminados), as=ED evitaremos el ruido =F3ptico. Lo segundo
es ensayar =
el m=E9todo=20
de apertura del diafragma sin que se nos mueva ni un =E1pice
la =
c=E1mara. Y lo=20
tercero es hacer las fotos, cuantas m=E1s mejor, con un
m=EDnimo de =
dos fotos=20
podemos obtener ya un hdr, pero lo normal es hacerlo con
tres, aunque =
yo he=20
llegado a hacer hasta siete tomas diferentes de la misma =
im=E1gen.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>En estas tomas
no tenemos la =
necesidad de valorar=20
el contraluz, ni por tanto la posici=F3n del sol respecto de
la =
c=E1mara, ni si=20
alg=FAnas partes de la im=E1gen quedar=E1n solarizadas, ni
siquiera si =
existe alg=FAn=20
objeto entre el foco luminoso y el objetivo, porque todos
estos =
obst=E1culos=20
habituales quedar=E1n superados con esta
t=E9cnica.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Pero s=ED
debemos valorar el tiempo =
de exposici=F3n,=20
o lo que es lo mismo la velocidad de obturaci=F3n del
diafragma, =
porque de ella=20
depende en gran medida la cantidad de luz que recibe nuestra
im=E1gen =
y la=20
definici=F3n de las texturas que
contiene.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Luego
guardaremos las im=E1genes en =
formato Tiff o=20
Psd y las volcaremos a nuestra computadora, donde las
podemos =
renombrar=20
(aunque no es estrictamente necesario, pero ayuda para=20
organizarse).</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Lo dem=E1s
ser=E1 todo hecho con =
nuestro viejo=20
conocido Photoshop, aunque solo admiten esta t=E9cnica las
versiones =
CS2 y CS3,=20
b=E1sicamente porque antes no se hab=EDa inventado, je, =
je.</FONT></DIV>
<DIV align=3Dright><FONT face=3DArial
size=3D2><EM>--->=20
contin=FAa</EM></FONT></DIV>
<DIV><FONT face=3DArial =
size=3D2></FONT> </DIV></BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_004C_01C816E0.3950EF70--

maybe OP want to extract all numbers from his inbox using regular expressions?

Automation server error 0x800a01ad

I've been able to batch delete, import, and export metadata from the XML file, but can't seem to import and export the binary thumbnails, raw books, and encrypted books.
As soon as I set ImportFiles:Yes and ImportRawBook:Yes, error 0x800a01ad "Automation server can't create object" is thrown.
Does anyone have any insight into this error message? I know it has been asked before about a comprehensive list of error messages, but Adobe seems unconcerned about supplying such resources to end users. I'm trying to gain enough knowledge to avoid the expensive per-incident support fees.

Mike,<br /><br />We import our books with the batch tool. Below is an example of how we write our XML file. Maybe it can help you. /Fabian<br /><br /><?xml version="1.0" encoding="ISO-8859-1"?><br /><acs:Message<br /> xmlns="http://www.editeur.org/onix-international/ReferenceNames/"<br /> xmlns:acs="http://www.glassbook.com/metadata-0.1"><br /> <Product><br /> <NotificationType>04</NotificationType><br /> <ISBN>9172970278</ISBN><br /> <DistinctiveTitle>Gomstallet</DistinctiveTitle><br /> <ContributorStatement>Marten Sanden</ContributorStatement><br /> <PublisherName>eLib</PublisherName><br /> <SupplyDetail><br /> <SupplierName>eLib</SupplierName><br /> <Price><br /> <PriceTypeCode>01</PriceTypeCode><br /> <PriceAmount>39</PriceAmount><br /> </Price><br /> </SupplyDetail><br /> <acs:RawBook><br /> <MediaFileFormatCode>04</MediaFileFormatCode><br /> <MediaFileLinkTypeCode>06</MediaFileLinkTypeCode><br /> <MediaFileLink>\\server\folder\ISBN9172970278.pdf</MediaFileLink><br /> </acs:RawBook><br /> <acs:PublishInfo><br /> <acs:RightCopyCount>0</acs:RightCopyCount><br /> <acs:RightCopyInterval>0</acs:RightCopyInterval><br /> <acs:RightPrintCount>0</acs:RightPrintCount><br /> <acs:RightPrintInterval>0</acs:RightPrintInterval><br /> <acs:RightLendHops>0</acs:RightLendHops><br /> <acs:RightUseExprirationType>4</acs:RightUseExprirationType><br /> <acs:RightTimeAllowed>0</acs:RightTimeAllowed><br /> <acs:RightUseExprirationDate>12/31/1969</acs:RightUseExprirationDate><br /> <acs:RightUseExprirationInterval>0</acs:RightUseExprirationInterval><br /> <acs:RightReadAloud>-1</acs:RightReadAloud><br /> <acs:RightModifyRights>0</acs:RightModifyRights><br /> <acs:Copies>1000000</acs:Copies><br /> <acs:ContentType>1</acs:ContentType><br /> <acs:EncFileName>ISBN9172970278.pdf</acs:EncFileName><br /> </acs:PublishInfo><br /> <acs:DeploySite><br /> <acs:KeyName>local</acs:KeyName><br /> <acs:DeployType>1</acs:DeployType><br /> <acs:DeployFlags>1</acs:DeployFlags><br /> </acs:DeploySite><br /> <acs:Approval>1</acs:Approval><br /> </Product><br /></acs:Message>

How do I extract my photographs EXIF metadata from Aperture using Automator?

I have the following Automator workflow
Get selected images
Filter for picks
Extract metadata (checked all fields)
New Text file
Open finder item (selected preferred application)
When run the text file just the exif fields has been exported with none of the metadata (eg shuuter speed, ISO etc)
what am I doing wrong?
Martin

Hi Frank
Frank Caggiano wrote:
That's a rough description of the workflow not the workflow.
Include the actual workflow it makes it a whole lot easier to troubleshoot.
Is this what you want?
This is my text file output. No metadata just the field names.
Name     IPTC Creator     IPTC Creator's Job Title     IPTC Caption     IPTC Category     IPTC Image City     IPTC Contact     IPTC Copyright Notice
IPTC Image Country     IPTC Provider     IPTC Headline     IPTC Keywords     IPTC Content Location Code     IPTC Content Location Name     IPTC Job Identifier
IPTC State/Province     IPTC Source     IPTC Special Instructions     IPTC Caption Writer     EXIF Aperture     EXIF Capture Day of Month     EXIF Capture Day of Week
EXIF Capture Hour of Day     EXIF Capture Month of Year     EXIF Capture Year     EXIF Color Model     EXIF Color Space     EXIF Contrast     EXIF Depth
EXIF EXIF Version     EXIF Exposure Bias     EXIF Exposure Mode     EXIF Exposure Program     EXIF Flash     EXIF Flash Pixel Version     EXIF Focal Length
EXIF ISO     EXIF Date     EXIF Camera Make     EXIF Max. Lens Aperture     EXIF Metering Mode     EXIF Camera Model     EXIF Pixel Height     EXIF Pixel Width
EXIF Profile Name     EXIF Saturation     EXIF Scene Capture Type     EXIF Sharpness     EXIF Shutter Speed     EXIF Software     EXIF White Balance
Hope you can help
Martin

Sorting lines by length in automator?

I have a document with around 4,000 lines of text. Is there a way for me to automatically sort them by character length through the use of Automator and a bit of scripting?
Bonus points if there's a way to output the character length at the beginning of each line once the sorting is complete.
Little heads up, my knowledge of AppleScript is pretty non-existant so an idiot's guide would be much appreciated.

There's nothing wrong with the script, it's the format of your text file that's causing the problem.
Unfortuntely there isn't really such as thing as a 'plain' text file anymore. Text files come in a variety of formats (ASCII, Unicode, ISO, etc.) and use varying line endings (CR, LF, or CR/LF), and the particular combination used in your file is breaking the script.
The simplest solution is to save the file as standard UTF-8 Unicode, then the script works fine. If you don't have an application that can convert it you can incorporate the command line utility textutil into your shell command:
textutil -convert txt -o - $1 | awk '{print (length($0) " " $0 "</sentence>")}' | sort -n
This time it will invoke textutil to convert the file first (rather than just cat, then run the awk/sort commands.

Adobe CS5 error Build .iso - Blu-ray Error: "device error", Code: "3", Note: "File can not o

Hi am trying to create a bluray image .iso i loaded the gritty submenu and modified it and am getting this error
and when i try to build it it giving me this error
Blu-ray Error: "device error", Code: "3", Note: "File can not open.(/Volumes/Mac HD1/Adobe Encore Projects/BD/AuthorScriptHDMVSessions/Gritty Noir Submenu HD_mm_1.m2v.00_00_00_1.1.1_UTC.ves) -
Anybody encountered this problem? Thanks I appreciate it.

Hi,
Remove the all the files from
/Volumes/Mac HD1/Adobe Encore Projects/BD/AuthorScriptHDMVSessions/
This will resolve this issue.
This happens if any file corrupted in Volumes/Mac HD1/Adobe Encore Projects/BD/AuthorScriptHDMVSessions/ folder
Thanks,
Pankaj Gauba

2011.11-1 archboot "2k11-R7" ISO hybrid image released

Hi Arch community,
Arch Linux (archboot creation tool) 2011.11-1, "2k11-R7" has been released.
To avoid confusion, this is not an official arch linux iso release!
Homepage and for more information on archboot:
http://wiki.archlinux.org/index.php/Archboot
Summary:
- Plain bugfix release.
Hybrid image file and torrent is provided, which include
i686 and x86_64 core repository. Please check md5sum before using it.
Hybrid image file is a standard CD-burnable image and also a raw disk image.
- Can be burned to CD(RW) media using most CD-burning utilities.
- Can be raw-written to a drive using 'dd' or similar utilities.
This method is intended for use with USB thumb drives.
Please get it from your favorite arch linux mirror:
https://downloads.archlinux.de/iso/archboot/2011.11/
<yourmirror>/iso/archboot/2011.11/
/boot for PXE/Rescue files are provided here:
https://downloads.archlinux.de/iso/arch … 11.11/boot
<yourmirror>/iso/archboot/2011.11/boot
Changelog:
GENERAL:
- kernel 3.1.1 / LTS kernel 2.6.32.48
- pacman 3.5.4 usage
- RAM recommendations: 320 MB
Kernel changes:
- bump to latest 3.1 series and bump lts to latest .32 series
Removed features:
- ide-blacklist hook for 3.1 series
Environment changes:
- updated pacman mirrorlist
- added efivars kernel module
- added real kernel version names to bootmessage
hwdetect changes:
- none
setup changes:
- fixed manual mounting of install media
- load efivars module for grub2 uefi support
- fix GPT detection on bootloader menu
quickinst changes:
- none
Further documentation can be found on-disk and on the wiki.
Have fun!
greetings
tpowa

/boot for PXE/Rescue files are provided here
I was wondering if there are any boot parameters available or planned to assist with automated network installations?
- E.g. I would like to have the network settings configured automatically.
I already tried using boot parameters in the standard form of: "ip=$ip::$gateway:$netmask BOOTIF=$mac" (filled in with the actual values by our pxe boot system)
But that results in an error:
/init_functions: line 86: [: !=: unary operator expected
Waiting 10 seconds for device ...
/init_functions: line: 90: [: too many arguments
ERROR: unable to determinate major/minor number of root device ''.
Judging by the "root device" message I think it automatically assumes I want some kind of NFS/NBD boot, but I just want to have the ip, netmask & gateway settings configured.
- Also I would like it to automatically download a configuration file and proceed with installation.
The wiki mentions automatic installations are possible: https://wiki.archlinux.org/index.php/Of … _Procedure
But that you have to invoke "aif -p automatic -c /path/to/configfile" from the command-line for that.
That does not sound very automatic to me.
Why not have a boot parameter like most other distributions have, along the lines of: "kickstart=http://my-server/configfile" ?
Last edited by Max (2011-12-08 19:27:52)

My kingdom for a BMAS 3.7 iso ...

I have to P2V an old server (hardware-wise) and keep Radius / FTP running. When I tried this last week, all but Radius started back up (I had copied all the pertinent NLM's from SYS.MIG). The license / DAS objects are still there, but the migrated server's Radius errors out with "Fail to register BorderManager Authentication Services licence"
Restoring DS and bringing back the physical server went ok, and Radius was fine ... What am I missing here?? Just in case, I would appreciate a link to a BM3.7 FCS iso file (I have BM37 SP3 to update later).
Thanks in advance!

cbardram,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://support.novell.com/forums/

AIF and automated installation

I have a bunch of machines to get installed. I am using the automated feature of AIF and so far I have two questions:
1 - Even selecting net as SOURCE and eth0="dhcp", I have to run the partial configuration of the network before the automatic installation. Is it a bug or a feature ?
2 - How can I add the configuration file in the same usb stick as the installer ? I am currently using two sticks or copying it through scp.
It is really a great tool.

tjpp wrote:
Thanks for your reply! It works with
worker_runtime_network () {
dhcpcd eth0
with dhcpcd rather than dhcpd.
sorry, i make this typo all the time.
tjpp wrote:1. the options I have in BLOCKDATA are not passed to the final /etc/fstab. Basically are ext4 performance options (data=writeback, for instance).
this is a bug that has been fixed in the meanwhile.
http://bugs.archlinux.org/task/18994
iirc the latest isos at http://build.archlinux.org/isos/ have the fix.
tjpp wrote:2. Is there a function like worker_intro () where I could put my scripts to run after core installation ? Is the worker_configure_system run after the packages installation ?
/usr/lib/aif/core/procedures/automatic should explain everything.

Merge all ISO images of Oracle Linux into a single ISO (single installation media)

Hi all,
I have downloaded Oracle Linux 7 ISO files :
V74844-01.iso (4.1GB)
V74845-01.iso (340 MB)
V74846-01.iso (3.4GB)
V74847-01.iso (2.1GB)
Is it possible to merge all these ISO files into a single bootable ISO file, and write it to a 16GB USB stick to use it as installation media?

f53ff284-8915-4e99-9a17-9a463de00c22 wrote:
Other than V74844-01.iso, which of the remaining 3 ISO file are important for a fully functional installation?
None of them. Only V74844-01.iso is required for a fully functional installation.
V74845-01 is a boot ISO and is used by network administrators when creating network-based automated boot/install solutions that require the installer to run the UEK instead of the RHCK. The default ISO uses the RHCK.
V74846-01 and V74847-01 contain the source code for all the packages that ship on V74844-01. This is required under the terms of the Open Source licenses under which Oracle Linux is shipped. This is only required if you want to modify and recompile any of the packages provided by Oracle Linux.

M2V to ISO Automation

Similar Messages

Maybe you are looking for