MSI X58A-GD65 new BIOS.
Customized settings are lost IssueDate identifiedThere are several possible causes for the corruption of files containing customized settings:. An application, process, or Windows itself shut down abnormally during a file write operationThis usually happens when something goes wrong while the file is being saved. The problem could be internet connectivity if the program is signed in to a service, or your computer suddenly loses power. Other problems include network issues, available computer resources, another running app or unstable process.
If any of these things interrupt the process of writing to the file, the entire file may not be written or the hard drive “table of contents” does not get updated. A physical hard drive is fragmentedThis only applies to physical hard drives.
Solid state drives are not affected. A fragmented hard drive creates more pieces in which the options.xml file will be stored. Upgrading the client or your operating system IssueDate identifiedFalse 'Unidentified publisher' system warning in Windows 7, 8/8.1, and Windows 10 upon startup of client 2.63If you use version 2.63 of the Connexion client in Windows 7, 8/8.1, or Windows 10, you receive the following Windows User Account Control (UAC) system warning each time you start the client:An unidentified program wants access to your computer.connex.exeUnidentified publisher'C:Program Files (x86)OCLCConnexionProgramConnex.exe'The enhanced security in modern versions of Windows triggers UAC when the client is started. Click Yes to grant permission. The client will open and run as expected.Downloading and installing the client will suppress UAC prompts when opening the client.Added: April 21, 2011Updated: September 21, 2018During upgrade, installation fails; you are asked for Connexion.msi pathIn some cases, the upgrade installation may fail with a message asking the path to your Connexion.msi file. Please contact for help in resolving this problem.April 11, 2011The installation program may re-run the first time you open the client after installing the client-only softwareIf this problem occurs, it happens only the first time you run the new version. Searching IssueDate identifiedChange to heading appearance of headings in a browse list when the ending punctuation of the heading is differentAs part of the Connexion install, changes have been made to authorities indexing.
These include the resolution of the longstanding problem that resulted in misleading subfield codes:'Occasionally, a heading appears in browse results with a subfield code that is misleading. However, when you view the record, the subfield code that appears in the results list is not present in the record.An example of this is browsing the LCSH index for the heading Noah's Ark. In the root index, the heading is presented as $t Noah's Ark; however, when you view the record, the heading Noah's Ark appears in $a, not $t.
There is only a single subject authority record for Noah's ark, in which the heading appears only in $a (LCCN sh 85092133). But the text Noah's ark appears in $t in 9 other authority records.”However, as part of the new indexing, users will find a change in the appearance of headings in a browse list when the ending punctuation of the heading is different. Editing IssueDate identifiedEdit a record, then save it, and then lock the record.
Your edits are lost.The client gives no warning but does not retain your edits in this workflow scenario.December 14, 2006Highlight with mouse from right to left to delete a field may shift data in next fieldHas been added as a to client documentation and Help.December 19, 2005Overwrite/insert editing mode changes incorrectlySometimes the editing mode shifts incorrectly in the client from overwrite to insert or vice versa. So far, the cause, circumstances, and frequency of this problem are undetermined. Constant data IssueDate identified250 field in Constant Data overwrites existing 250 field when appliedThe client does not recognize that the 250 field is repeatable. As a result, a 250 field in a constant data record will overwrite an existing 250 field when constant data is applied to bibliographic record.Workaround: Enter the text you want to add to the 250 field in a tag that is not often used, and then change the tag number to 250 after you apply constant data.March 11, 2016For online constant data (CD) only, diacritics and special characters in CD name and CD My Status cause errorsHas been added as a to client documentation and Help in the same topic specified in the known problem directly above.
The cautionary note has a list of the characters that cause errors.December 14, 2006Save constant data from the local save file to the online save file fails if online record already has a record with the same nameHas been added as a to client documentation and Help in Cataloging/ Use Bibliographic Constant Data, 'Create, edit, or delete bibliographic constant data.' December 19, 2005. Taking actions IssueDate identifiedFalse error message may result from system duplicate detection when new authority records are added or master records are replacedThe system uses NACO Normalization rules to match the 1XX heading of any record you want to add or replace against the 1XX and 4XX name headings to detect duplicates. However, the system incorrectly ignores the first comma in subfield a, which results in an incorrect validation error message— This main entry exists in another authority record: LCCN=xx xxxxx ARN=ocaxxxxx. If you receive this message as a result of this problem, and the new/replace heading is not a duplicate, click OK to close the message, and simply re-issue the Add or Replace command to successfully add or replace the record.June 14, 2006Inappropriate message may appear when exporting authority recordsOn occasion, you may receive the following message when you export authority records: 'This main entry exists in another authority record: LCCN=n ######## ARN=oca########.' You receive the message as a result of a process that normalizes the main entry to help reduce duplicate records. Currently, tags are not considered in the normalization process.The message occurs when you validate the record (Edit, Validate) before exporting or when you have the validation level set to 'Full' in the Tools, Options, General tab (click Validation Level Options).If you used Edit, Validate, you can go ahead and export with no problem.
If you have the validation level set to 'Full,' change it to 'Basic' and then export the record.December 19, 2005. Controlling headings IssueDate identifiedSpace required between subfield delimiter and heading text in version 2.63Client version 2.63 requires a space between other characters in the text of the field and the subfield delimiter to control a heading. The move to support all Unicode characters has changed the behavior of Latin Letter Aveolar (U+01C2) that the client uses for the delimiter symbol. Reformatting the record before you control headings adds the spaces automatically.February 9, 2017Headings seem controllable but cannot insert them into bibliographic recordThere are situations in which headings are presented as controllable, but when a user attempts to insert them the heading is not successfully inserted into the bibliographic record.
An example of this is when attempting to control the heading:600 10 Mah, Stuart $v Correspondence.The following headings are presented in the Control Headings window:Mah, Stuart ‡t Correspondence Mah, Stuart. ‡t Correspondence. 600 Partially-controlledMah, Stuart ‡v Correspondence Mah, Stuart ‡v Correspondence. 600 Fully-controlledMah, Stuart. 600‡v Correspondence Subdivision recordBoth headings are presented with the option to either Modify Heading or Insert Heading. But at this time, if a user attempts to insert the heading, other pages are presented but the user cannot successfully insert the heading.The workaround for this problem is:In the display window, one of your options is the name heading alone, without subdivisions.Mah, Stuart. 600Click the Modify Heading button.In the window, you should then see your subfield $v 'Correspondence'.
Click the Append to Heading button beside it. Transliteration, diacritics, non-Latin scripts IssueDate identifiedCursor does not always display at the end of the text when non-Latin script characters are pasted into a fieldWhen non-Latin characters are pasted into a field, the cursor may display in the middle of the text instead of at the end.February 21, 2018Latin Letter Aveolar (U+01C2) and Khosian LanguagesThis character is also the subfield delimiter symbol in the client. The client interprets this character as a subfield delimiter and errors will occur if you attempt to use it in your bibliographic records for items in Khosian languages.
Other IssueDate identifiedUnable to open external links in Online HelpThe online help system in Connexion client is having some compatibility issues with some of the external web pages to which it links.Workaround:If you are having difficulty opening an external web page, you can copy the web address from the Properties dialog, which is available on the right-click menu for the web link. To open the web site, you can then copy this information and paste it directly into address field for your browser. You can also search for the content on the OCLC Support site or open the links from the documentation that is found on the Connexion Support Web site.November 5, 2014Cannot maximize (re-display) Connexion client from a minimized position in the task barWhen you minimize the Connexion client, it becomes an icon in the task bar on your desktop, and you should be able to maximize (re-display) it by clicking the icon.
If you are unable to maximize the client from the task bar icon, use the following workaround.Workaround: Click the Connexion client icon in the task bar, and then press and hold the Windows key ( ) on your keyboard while you click the key.September 21, 2011Catalogers can use Connexion client 2.00 and higher via a Citrix thin client, with caution and with some limitationsOCLC has completed limited testing using version 2.00 under Citrix access. Though most functionality appears to work under testing conditions, except the two functions listed below, OCLC does not guarantee that the client will work for everyone under Citrix, since server and system configurations vary from library to library.The following are known limitations of using the client under Citrix:. You cannot use macros (although staff at one library reported that their Citrix implementation contractor developed a customized way for them to use macros). Writing data to a file may not work. Examples of writing to files in the client include exporting records to a file and printing records, labels, or an accession list to a file. Writing data to a file under Citrix creates files on your remote server. Depending on the location of the files, you may not have access to them.
Resulting error messages are 'exceptions' that do not explain that this is the problem.July 27, 2007Updating holdings on records imported into the client via Z39.50 (Tools menu) does not workIf you use Update Holdings to add a Z39.50-retrieved local system record to WorldCat (the client imports the record as a workform), you receive a message that field 001 is missing the OCLC number. As a workform, the record should not have an OCLC number in field 001. This is a system error.Workaround: Derive a new record from the Z39.50 imported record and then add to WorldCat using Update Holdings.July 27, 2007. Problems resolved in version 2.51 IssueDate IdentifiedIn client version 2.50, some Extended Latin characters do not export correctly when MARC-8 character encoding is used for export. (RESOLVED)In client version 2.50, when ToolsOptionsExportRecord characteristicsCharacter set is set to MARC-8, these characters will export as numeric character references instead of the actual character.
These characters export correctly when UTF-8 is selected for export. Latin capital letter D with stroke.
Latin small letter D with stroke. Latin small letter dotless I. Latin capital letter L with stroke. Latin small letter L with stroke. Latin capital ligature OE. Latin small ligature OE.
Latin capital letter O with horn. Latin small letter O with horn.
Latin capital letter U with horn. Latin small letter U with hornAdded: March 10, 2014Resolved: April 16, 2014.
Ok this is going to sound crazy but here we go!
Today I’m migrating this old SQL 7/Windows 2000 database server from VMWare ESX 3.5 to Proxmox VE. However this server started out on a VMWare ESX 2.5 server. And in the subsequent years had been decommissioned , and never updated but rather just copied onto the 3.5 cluster as we decommissioned the 2.5 cluster. At least I figured disk space was cheap enough we should keep the old VMs that “we will never need again” because.. Eventually someone will panic, and realize they need it again.
In the first step of doing so I needed to remove the old version of VMWare tools. But the catch is, this old version requires you to have the msi package handy to remove it. Well isn’t that a fun little catch. And you’ll find all kinds of ideas on what to do now that you don’t have your original “VMWare Tools.msi”. And more importantly you’ll now realize that you should have not only saved your old ISOs of ESX, but you should have also pulled out the tools ISOs and saved them as well.
Luckily I did save the software keys thought! Although I suspect that is also somewhere on their website, but they make it a chore to find the old stuff.. At any rate with 30 minutes of searching I finally came across the last version of 2.5, ESX Server 2.5.5 Build 57619.
Now it would seem that the VMWare tools are kept in an RPM file. Which is going to be a major pita for me to extract on Windows so I decided to take the more insane route, and install ESX on Qemu!
First I create a 5GB IDE disk to boot VMWare ESX server off, and a 10GB SCSI disk for the vmfs.
qemu-img.exe create -f raw esx25.disk 5G
Formatting ‘esx25.disk’, fmt=raw size=5368709120
qemu-img.exe create -f qcow2 esx-scsi.disk 10G
Formatting ‘esx-scsi.disk’, fmt=qcow2 size=10737418240 encryption=off cluster_size=0
With the disks created, I then fire up Qemu like this:
qemu-system-x86_64 -cpu Opteron_G2 -L pc-bios -m 512 -hda esx25.disk -drive file=esx-scsi.disk,if=scsi,bus=0,unit=0 -option-rom 8xx_64.rom -net nic,model=e1000 -net user -net nic,model=e1000 -redir tcp:8088::80 -redir tcp:8022::22 -redir tcp:8433::443 -cdrom installesx-2.5.5-57619.iso -boot d
This pulls in a few things, the SCSI configuration along with the AMD CPU type configuration that I’ve touched on previously.
And away we go!
And Qemu should easily boot the graphical installer.
ESX 2.5 system
So using my configuration, I dedicate one Ethernet card to ESX, another to the guests, and share the SCSI adapter between the console and the guests…
And when it comes to the partitioning, I simply extended the root partition to the rest of the drive, and setup vmfs2 on the SCSI disk. I’m not even thinking about clustering, I’m primarily after the extensions.
Installation takes about 20 minutes. It is just the way it is. The pegasus cimom for linux takes forever, along with the provider-esx package. I have no idea why, it’s probably thousands of little files or something crazy like that. But be patient, it’ll install.
ESX 2.5 installed
And there we go, a successful installation!
Now VMWare will want to reboot, I just kill Qemu, and then launch it booting off the IDE harddisk (-boot c).
ESX 2.5 boot options
Now we get an ESX and Linux boot menu. I’m feeling brave, so let’s try to boot ESX!
It’s loading…
And it panics. Bug 1406:2154 BugNr=34866
“measured cpu and bus speeds conflict”
Oh well. But we can boot into Linux, and scp out the extensions! Which do hide in /usr/lib/vmware/isoimages/windows.iso . So it’s not a total loss. I did notice on VMWare Fusion there was a setting for ESX, perhaps I can run ESX 2.5.5 on my Mac? Perhaps, but I’ll try that for later.
Now with the ISO finally in hand, I put it in my VM, and tell it to uninstall the extensions, I provide it with the VMWare Tools.msi and I get…
The file VMWare Tools.msi is not a valid installation package for the product VMware Tools.
Try to find the installation package ‘VMware Tools.msi’ in a folder from which you can install VMware Tools.
However the ISO did offer a chance to ‘upgrade’ my apparently older 2.5 extensions. So I did that, rebooted, then with a matching level ISO I was able to remove them. Wow was that convoluted! If anything I guess we’ve found out you want to hold onto these extension CD’s not matter what.. You never know if someone comes in with an old VM, or if you had a decommissioned VM that suddenly has to be brought back to life, it’s best to have these handy to get them back into shape. Just because your setup is all ‘complete’ it doesn’t stop people from throwing you curve balls.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
March 2023
Categories |