Colorman3605 Posted June 22, 2020 Share Posted June 22, 2020 I can no longer run the eXoDOS block setup file to unpack all the files. To be precise, it starts but I say that I am missing the util.zip file. The fact that the file is present. What is the problem and how can it be solved? Thank you! Quote Link to comment Share on other sites More sharing options...
neil9000 Posted June 22, 2020 Share Posted June 22, 2020 7 minutes ago, Colorman3605 said: I can no longer run the eXoDOS block setup file to unpack all the files. To be precise, it starts but I say that I am missing the util.zip file. The fact that the file is present. What is the problem and how can it be solved? Thank you! Pass, try asking @eXo exodos is not a official Launchbox product, so its not a Launchbox problem per se. Quote Link to comment Share on other sites More sharing options...
eXo Posted June 22, 2020 Share Posted June 22, 2020 did you maintain the folder structure or try just dumping it all into the same folder? because it doesn't work like that. Quote Link to comment Share on other sites More sharing options...
Colorman3605 Posted June 22, 2020 Author Share Posted June 22, 2020 (edited) I copied all the files to a folder called MS-Dos, keeping all the files intact This is the structure of the files and folders (the folders are all in capital letters. In the GAMES folder there are the zip files of the games): MS-DOS EXODOS EXODOS GAMES ...... UTIL unzip.exe util.zip EXTRAS ! DOSmetadata.zip _ReadMe_.txt eXoDOS Catalog.pdf eXoDOS Manual.pdf eXoDOS ReadMe.txt LaunchBox.zip SETUP.BAT XODOSMetadata.zip I also tried without the first folder (MS-DOS) but the setup always tells me that the util.zip file is missing (even if it is present). Edited June 22, 2020 by Colorman3605 Quote Link to comment Share on other sites More sharing options...
xanthrax Posted March 2, 2023 Share Posted March 2, 2023 Sorry for bringing this old topic back to life, but did you ever manage to fix this problem? I have the same problem. Files are in proper place but it asks for util.zip even though it's there. Quote Link to comment Share on other sites More sharing options...
cubsfan61 Posted October 3, 2023 Share Posted October 3, 2023 I'm also having the same issue. Setup.bat won't run unless run as Administrator (can't find setup.bat, which is the file being run?????). It can't find util.zip even though it's in the folder that it's expecting it to be in. Same issue setting up EXOWIN. Quote Link to comment Share on other sites More sharing options...
dankell Posted October 6, 2023 Share Posted October 6, 2023 (edited) Hello Guy`s . Any help with this issue? I also have this same problem as others have stated. I downloaded the torrent eXoDOS_Lite from eXo`s main site onto a 120GB SSD so the download structure is as what was downloaded, no modifications , I open the eXoDOS_Lite folder and run the setup.bat as Administrator and get the Exact same error as the other Guy`s. Any help here much appreciated. Thank you all for any feedback. PS: Running Setup from a SSD 120GB USBC External, Windows 10 Pro x64 Update: Found the solution Guy`s. Strange as it may seem ... DON`T run the .bat setup file as Administrator fixed the problem. Hope it helps some of you too facing this problem. Best Regards, Edited October 7, 2023 by dankell Quote Link to comment Share on other sites More sharing options...
cubsfan61 Posted October 10, 2023 Share Posted October 10, 2023 If I run setup.bat without using Administrator, I get a windows message saying it can't find setup.bat (which is weird since that's the file I'm running). Same as dankell, I'm using the files in the same structure as downloaded. Quote Link to comment Share on other sites More sharing options...
ezgoodnight Posted December 28, 2023 Share Posted December 28, 2023 Going to bump this old thread because I feel like I have the solution, or at least something that might be causing problems for everyone else. Also this thread comes up as a top result when I google the problem. I was using the script on a network share, and this was the issue. When I moved it to a network DRIVE the windows machine/Powershell saw the script and relative paths as normal. It was probably something as fragile as an illegal character issue breaking the script and causing it to not see the folder structure. So: 1. exoDOS folders on local or network drives only, no shares with IP addresses, just D, E, F, etc drives. 2. powershell as admin This seems to solve the issue. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.