gho naming limitations?
Kurbycar32
August 24th, 2009
ive been making ghost images for years so for a few models i have several versions available. my naming convention is pretty simple being the model and version, for example my dell latitude d600 image is currently "D600v5" being the version 5 image. creating the images using these names goes off without a hitch but sometimes when my techs are deploying these images in the field the GHS file isnt found. if i rename the ghs file from "d600v5001" to "d6005001" (removing the V) the ghs file is found and everything is fine. so the question is are there limitations to the naming of gho and ghs files and should i probably be naming these something different?
Stick to 8.3 format
You don't mention the version of Ghost you are using, but from your description, where you have shortened the filename from 9 characters to 8 to get it to work, I suspect you have a version of 8 or less, and perhaps are booting off a DOS diskette.
So if you stick to a naming convention that is entirely DOS compatible - ie the old 8.3 format, you should have no problems.
If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.
sorry its ghost solution
sorry its ghost solution suite 2.5 so thats ghost 11.5 and i have all the updates.
i am using a dos based boot image but its being hosted by a 32bit ghostcast server on a windows machine so i would think there wouldnt be an 8 character limit, your theory makes sense though
4 character
as a test i created my latest image (different model) and named the image "DCv6.gho" the span was automatically named "DCv6001.ghs". the image was created using a 2008 64bit server if that changes anything. my tech in the field hosting the image from her 32bit xp machine gets the error "DCv60001.ghs could not be found" so its obviously looking for the wrong file name and i dont think its because the name was too long
Would you like to reply?
Login or Register to post your comment.