![]() ![]() Going back through the log and looking at the API errors may give you a pretty direct hint as to the source of the problem if there are API errors, the context of those errors may give a pretty big hint (and of course, since Process Monitor captures the running program's execution state for each call, a Process Monitor trace is a prime source of evidence for the developers to use - when Ghost development was in Auckland it would have been trivial to get such a log examined and an authoritative answer, although now it's a different story). That won't always be true when working with real optical disks (as the SCSI pass-through stuff is kinda special) but when writing to a target that's just an ordinary file then everything is plain Win32 APIs which Process Monitor logs just fine. If you get a detailed trace of what the GBW is doing from the start right up to the point where it fails, generally at the end of the trace you'll see some kind of operations issued by the GBW executable which yield a failure at the API level which Process Monitor will capture. Probably the best thing to do at this point is the obvious one: use Process Monitor. That's most notable because there's almost nothing in common between the floppy write (VFD being specialized off the floppy code) and the ISO write - there's basically no code at all shared between the two systems because floppies and ISOs have nothing at all in common - different filesystem, different media model in the code, it's all different. Just about the only thing that *is* shared is the data in the source templates. However, the one thing that's really different in your report from the norm is this:Īlthough same error occurs when trying VFD So in general, the source of this particular error is impossible to answer - there are far too many cases which will generate it. If you have a +R or -R type disc that has any data on it at all, you can't use it. The number of other things which end up producing the same message also includes particular species of existing formats on the disc, for instance, because the existing GBW code doesn't even try to model the different optical disc write models nor support UDF. There are a great many things in the GSS 2.5 series of GBW that produce that error insufficient space and >2Gb files are just the most common ones, but there are all kinds of other bugs both in the code which produces ISO 9660 filesystems (which fails if too many files are added to the ISO, for instance when including the DeployAnywhere driver database) and the code which does the SCSI wrangling of the optical disk command set. The second system has no AV, isn't part of a domain and no policies other than the default so I'm fairly certain it's the boot wizard doing this by itself.Ĭhristchurch (earthquake capitol of the world ) the first one is part of a domain and has the latest patches and global policies which i thought may have affected the installation or process. I've installed the boot wizard to 2 systems now. ![]() I'm hoping that someone can provide a reason for this. I remove this attribute and tell it to retry, but the same error occurs and the read-only attribute is re-appearing. Whilst the files appear to be created in the temp folder, the wizard is also making portions (or all) of this folder "read-only". It's when it attempts to copy thru the config.sys, autoexec.bat files etc that the problem occurs. As the wizard compiles the image files and puts them into a temp folder all is fine. I've spent further time trying to identify the issue and think I've located the problem. I've confirmed total ISO was below 4GB and each file was within the 2GB limit. I wasn't interested in the WinPE solution, just wanting a very basic PC-DOS boot session on a DVD aling with the image file(s). When I searched I found this article and tried to determine what is causing it. Please check that the target is not Read-only and there is enough space on the disk" Which is "An unexpected error has occurred. I am trying to create an ISO image (although same error occurs when trying VFD and a few others I've tried). No later update appears to be available presently. as per ghost explorer and ghostcast server apps). ![]() I've just upgraded to Ghost Solution Suite 2.5.1 (build 11.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |