I have a new Dell Precision-390 Workstation (lovely machine - unbelievably quiet).
I tried to follow the instructions to create an ISO
- Downloaded ubcd4win v3.0 (first was shown 3.4 but totally different than web instructions)
- Copied my "Reinstallation CD" of XP-Pro with SP2 to a directory - had a checksum error in the DONTNETFX directory that I had to ignore after trying multiple times)
- Followed the creating instructions - including updating all the files for which that was possible
- Started the ISO creation and got the following messages (lots left out)
Help. What do I do now.
My thanks
Jim Mitchell
****************************
UBCD4Win PE Builder 3.1.10a
Copyright © 2004-2006 .
Running OS Version: 5.1.2600 (Service Pack 2)
Source product is: Windows XP Professional
CD-Rom name is: Windows XP Professional Service Pack 2 CD
Microsoft Product Code: 76487
Product channel ID is: OEM
Warning: building from an OEM version of Windows can mean trouble...
Source build: 2600
Build process started
Removing directory: C:\tmpC\ubcd4win30\BartPE
Removing existing hive files
Loading: C:\TMPC\UBCD4WIN30\BARTPE\I386\SYSTEM32\setuphiv
Error: loadKey() failed:
Processing INF file "C:\tmpC\ubcd4win30\UBCD4WinBuilder.inf"
Saving hive: C:\TMPC\UBCD4WIN30\BARTPE\I386\SYSTEM32\CONFIG\DEFAULT
Closing hive: C:\TMPC\UBCD4WIN30\BARTPE\I386\SYSTEM32\CONFIG\petmphive
Error: closeHive() failed: RegUnLoadKey (key="PEBuilder.exe-C:/TMPC/UBCD4WIN30/BARTPE/I386/SYSTEM32/CONFIG/petmphive") returned error 0: Access is denied.
Creating file: default.log
Creating file: software.log
Cleanup temporarily files
Error: DeleteFile() "C:\TMPC\UBCD4WIN30\BARTPE\I386\SYSTEM32\CONFIG\petmphive" failed
Error: DeleteFile() "C:\TMPC\UBCD4WIN30\BARTPE\I386\SYSTEM32\CONFIG\petmphive.log" failed
Error: DeleteFile() "C:\TMPC\UBCD4WIN30\BARTPE\I386\SYSTEM32\setuphiv" failed
Error: DeleteFile() "C:\TMPC\UBCD4WIN30\BARTPE\I386\SYSTEM32\setuphiv.log" failed
Collecting files
Processing INF file "D:\Temporary 390\XPCD\I386\layout.inf"
Processing OEM file: C:\tmpC\ubcd4win30\drivers\SCSIAdapter\VIA\sata_raid_ide_s\TXTSETUP.OEM
SCSI hardware ID: VIARAID_VT3149_XP, component: VIA Serial ATA RAID Controller(Windows XP)
Adding PnP ID: PCI\VEN_1106&DEV_3149
Processing OEM file: C:\tmpC\ubcd4win30\drivers\SCSIAdapter\Ximeta\ALL_NetDisk\txtsetup.oem
SCSI hardware ID: NetDisk_XP, component: WinXP Ximeta NetDisk Network Drives NDAS
Checking for missing files
Warning: File "megasas.sys" not found
Builder has stopped because there are 4 build errors
ISO image is not created, you must fix the errors!
Building done...
There where 4 errors and 2 warnings
Full Version: Help Creating Disk for Dell Precision 390
This will link to the post that links to ones that explains the error and and the resolution...
http://www.911cd.net/forums//index.php?sho...amp;#entry87988
You can thank Dell for this one
http://www.911cd.net/forums//index.php?sho...amp;#entry87988
You can thank Dell for this one
Thanks for the quick response.
I'm afraid I'm scared off by futzing. I'll just stick with plain ubcd and hope nothing goes too wrong.
Jim Mitchell
I'm afraid I'm scared off by futzing. I'll just stick with plain ubcd and hope nothing goes too wrong.
Jim Mitchell
There's not much you can futz if you follow the directions that were posted. If all else fails then you could simply delete the directory that you copied your re-install cd to and that would be the end of futzing...
If you're not comfortable with futzing then I completely understand but if you want to get a working UBCD4Win cd built then we can most likely help you.
BTW. read my signature...
If you're not comfortable with futzing then I completely understand but if you want to get a working UBCD4Win cd built then we can most likely help you.
BTW. read my signature...
How in the world could anyone not want to futz?...... most people want to futz first, then post that they have problems and expect us to figure out what the hell went wrong. 
QUOTE (dirkgently42 @ Dec 16 2006, 05:03 AM) 
How in the world could anyone not want to futz?......
What the hell is the meaning of : futz ???
Joshua
OK - Your convincing me to try and futz. But I'm going to display my wet feathers:
I need help understanding what to do here. I:
- downloaded subinacl.exe and installed it
- copied subinacl.exe to the i386 folder where I have my XP disk copy
- copied the code and saved it as fixdell.cmd in that same i386 folder
- tried just double clicking subinacl.exe - it didn't do anything (as I expected)
- tried to get a command line so I could run it with fixdell.cmd as a run parameter - I don't remember my DOS well enough to be able to switch to to the directory it's in:
D:\Temporary 390\XPCD\I386\subinacl.exe
My Questions:
- Am I trying to do the right thing?
- If so how do I "run the script"?
- Is it necessary to edit the code first with the three items at the bottom 1.1-1.3 - I doubt it, but am unsure
********* http://www.911cd.net/forums//index.php?sho...p;p=82846&#
I have another freeware solution.
It requires this tool from Microsoft subinacl
Copy both the batch script below and the installed subinacl.exe from above link into the same directory as your setupreg.hiv and run the script.
fixdell.cmd
CODE
REM Version 1.2
reg query HKU | find /i "pebuilder" > fixdell.txt
for /f %%a in (fixdell.txt) do reg unload %%a
reg load HKLM\DELL setupreg.hiv
subinacl /subkeyreg hkey_local_machine\dell\controlset001\services\iastor\ /objectcopysecurity=hkey_local_machine\dell\controlset001\services
reg unload HKLM\DELL
del fixdell.txt
del /ah setupreg.hiv.log
echo Check output to see if there are any errors.
pause
What this does is replace the security settings on the iastor key with the ones in the the key above it. smile.gif
Edit:
1.1 Added a line to delete the .log file made by this fix.
1.2 Added routine to unload the hives which pebuilder was unable to unload.
1.3 Added a pause so you can see if there were any errors (Thanks to Fixxer for pointing out the idea)
You probably will want to get the dell fix plugin after this is fixed.
http://www.911cd.net/forums//index.php?sho...mp;#entry104627[url]
The original file came from the pebuilder website:
[url=http://nu2.nu/pebuilder/files/fixdellxp.cab]http://nu2.nu/pebuilder/files/fixdellxp.cab://http://www.911cd.net/forums//index....s/fixdellxp.cab
This copies the files: iastor.sys a320raid.sys aarich.sys aac.sys cercsr6.sys afamgt.sys NvAtaBus.sys nvraid.sys to your image.
I need help understanding what to do here. I:
- downloaded subinacl.exe and installed it
- copied subinacl.exe to the i386 folder where I have my XP disk copy
- copied the code and saved it as fixdell.cmd in that same i386 folder
- tried just double clicking subinacl.exe - it didn't do anything (as I expected)
- tried to get a command line so I could run it with fixdell.cmd as a run parameter - I don't remember my DOS well enough to be able to switch to to the directory it's in:
D:\Temporary 390\XPCD\I386\subinacl.exe
My Questions:
- Am I trying to do the right thing?
- If so how do I "run the script"?
- Is it necessary to edit the code first with the three items at the bottom 1.1-1.3 - I doubt it, but am unsure
********* http://www.911cd.net/forums//index.php?sho...p;p=82846&#
I have another freeware solution.
It requires this tool from Microsoft subinacl
Copy both the batch script below and the installed subinacl.exe from above link into the same directory as your setupreg.hiv and run the script.
fixdell.cmd
CODE
REM Version 1.2
reg query HKU | find /i "pebuilder" > fixdell.txt
for /f %%a in (fixdell.txt) do reg unload %%a
reg load HKLM\DELL setupreg.hiv
subinacl /subkeyreg hkey_local_machine\dell\controlset001\services\iastor\ /objectcopysecurity=hkey_local_machine\dell\controlset001\services
reg unload HKLM\DELL
del fixdell.txt
del /ah setupreg.hiv.log
echo Check output to see if there are any errors.
pause
What this does is replace the security settings on the iastor key with the ones in the the key above it. smile.gif
Edit:
1.1 Added a line to delete the .log file made by this fix.
1.2 Added routine to unload the hives which pebuilder was unable to unload.
1.3 Added a pause so you can see if there were any errors (Thanks to Fixxer for pointing out the idea)
You probably will want to get the dell fix plugin after this is fixed.
http://www.911cd.net/forums//index.php?sho...mp;#entry104627[url]
The original file came from the pebuilder website:
[url=http://nu2.nu/pebuilder/files/fixdellxp.cab]http://nu2.nu/pebuilder/files/fixdellxp.cab://http://www.911cd.net/forums//index....s/fixdellxp.cab
This copies the files: iastor.sys a320raid.sys aarich.sys aac.sys cercsr6.sys afamgt.sys NvAtaBus.sys nvraid.sys to your image.
Double click the fixdell.cmd file to run it.
QUOTE (pcuser @ Dec 16 2006, 10:52 AM)
Double click the fixdell.cmd file to run it.
Ah. That got me further - thanks. I was able to create the iso and boot from the CD.
Now, however, I get the message that megasas.sys is not found and termination of the boot.
It's possible that's a file that couldn't be copied from my dell disk (CRC error as I remember it). I looked in my machine's windows folder and couldn't find one there.
What next? I'm still willing to futz. And thanks for the help.
open the UBCD4WinBuilder.inf file in the root of your build directory and add this line to the [SourceDisksFiles] section:
CODE
megasas.sys=4,,4
QUOTE (AEngineer @ Dec 16 2006, 06:12 PM)
Now, however, I get the message that megasas.sys is not found and termination of the boot.
look here:
http://www.ubcd4win.com/forum/index.php?showto...gasas\.sys
Joshua
QUOTE (Joshua @ Dec 16 2006, 12:28 PM)
QUOTE (AEngineer @ Dec 16 2006, 06:12 PM)
Now, however, I get the message that megasas.sys is not found and termination of the boot.
look here:
http://www.ubcd4win.com/forum/index.php?showto...gasas\.sys
Joshua
I looked there and followed it down to what seemed to be "give up - buy a retail version" - not very helpful.
I looked on the Dell CD and found the MEGASAS.SYS file in I386.
I copied it over into my temporary I386 folder and reran the ISO builder.
Again I got the warning that it couldn't find megasas.sys - even though it was present - and again the CD crashed after burning it, telling me that it couldn't find megasas.sys.
hmmmm
Hi AEngineer
the location for device driver MEGASAS.SYS
is BARTPE\I386\System32\drivers not BARTPE\I386\
put it in correct location and rebuild ISO
if MEGASAS.SYS was in I386 folder containing Dell XP source then adding line in a plugin UBCD4WinBuilder.inf
would put it in correct location next time you rebuild ubcd4win / bartPE
regards
Mike Barnes
the location for device driver MEGASAS.SYS
is BARTPE\I386\System32\drivers not BARTPE\I386\
put it in correct location and rebuild ISO
if MEGASAS.SYS was in I386 folder containing Dell XP source then adding line in a plugin UBCD4WinBuilder.inf
CODE
megasas.sys=4,,4
would put it in correct location next time you rebuild ubcd4win / bartPE
regards
Mike Barnes
Read the post I made 15 minutes after you posted the megasas.sys error 
Oh how I hate to feel stupid.
A. ubcd4win has a folder BartPE, which has a folder I386 which has a folder SYSTEM 32
C:\tmpC\ubcd4win30\BartPE\I386\SYSTEM32
B. My temporary folder for the Dell windows files has the same two subfolders
D:\Temporary 390\XPCD\I386\SYSTEM32
Neither A nor B has a folder named "drivers" in System32
- the ubcd4win30 folder which contains the BartPE folders has a folder named drivers with a sub folder structure within it:
C:\tmpC\ubcd4win30\drivers
Should I put the MEGASAS.SYS in the folder?
C:\tmpC\ubcd4win30\drivers
Should I create a folder named drivers in the temporary XP folder location and put Megasas.sys there?
I note that there is a 63MB "driver.cab" file in the I386 folder
ALSO
IS this right for the modifying of the ubcd4wiinbuilder.inf file?
Does it matter where I put the modification you suggest?
*********
; PE Builder v3 INF file
; Created by Bart Lagerweij
; http://www.nu2.nu/pebuilder/
;
; More information about the format of this file, see pluginformat.htm
[Version]
Signature= "$Windows NT$"
[SourceDisksFiles]
bartpe.exe=2,,1
bartpe.txt=2,,1
biosinfo.inf=2
halaacpi.dll=2
halacpi.dll=2
halapic.dll=2
netmscli.inf=20
netnb.inf=20
nettcpip.inf=20
ntoskrnl.exe=2,ntkrnlmp.exe
bartpe.bmp=2
setupldr.bin=1
;
; 12/16/2006 JEM added the following on instructions of Mike Barnes in Forum
megasas.sys=4,,4
;
....... etc
Jim Mitchell
A. ubcd4win has a folder BartPE, which has a folder I386 which has a folder SYSTEM 32
C:\tmpC\ubcd4win30\BartPE\I386\SYSTEM32
B. My temporary folder for the Dell windows files has the same two subfolders
D:\Temporary 390\XPCD\I386\SYSTEM32
Neither A nor B has a folder named "drivers" in System32
- the ubcd4win30 folder which contains the BartPE folders has a folder named drivers with a sub folder structure within it:
C:\tmpC\ubcd4win30\drivers
Should I put the MEGASAS.SYS in the folder?
C:\tmpC\ubcd4win30\drivers
Should I create a folder named drivers in the temporary XP folder location and put Megasas.sys there?
I note that there is a 63MB "driver.cab" file in the I386 folder
ALSO
IS this right for the modifying of the ubcd4wiinbuilder.inf file?
Does it matter where I put the modification you suggest?
*********
; PE Builder v3 INF file
; Created by Bart Lagerweij
; http://www.nu2.nu/pebuilder/
;
; More information about the format of this file, see pluginformat.htm
[Version]
Signature= "$Windows NT$"
[SourceDisksFiles]
bartpe.exe=2,,1
bartpe.txt=2,,1
biosinfo.inf=2
halaacpi.dll=2
halacpi.dll=2
halapic.dll=2
netmscli.inf=20
netnb.inf=20
nettcpip.inf=20
ntoskrnl.exe=2,ntkrnlmp.exe
bartpe.bmp=2
setupldr.bin=1
;
; 12/16/2006 JEM added the following on instructions of Mike Barnes in Forum
megasas.sys=4,,4
;
....... etc
Jim Mitchell
QUOTE (mbarnes @ Dec 16 2006, 05:48 PM)
Hi AEngineer
the location for device driver MEGASAS.SYS
is BARTPE\I386\System32\drivers not BARTPE\I386\
put it in correct location and rebuild ISO
if MEGASAS.SYS was in I386 folder containing Dell XP source then adding line in a plugin UBCD4WinBuilder.inf
would put it in correct location next time you rebuild ubcd4win / bartPE
regards
Mike Barnes
the location for device driver MEGASAS.SYS
is BARTPE\I386\System32\drivers not BARTPE\I386\
put it in correct location and rebuild ISO
if MEGASAS.SYS was in I386 folder containing Dell XP source then adding line in a plugin UBCD4WinBuilder.inf
CODE
megasas.sys=4,,4
would put it in correct location next time you rebuild ubcd4win / bartPE
regards
Mike Barnes
One area you do need to address... the location of the XP CD files..
Do not use a location with spaces in the name
QUOTE
D:\Temporary 390\XPCD\I386\SYSTEM32
Do not use a location with spaces in the name
Don't feel stupid!
The changes you made to UBCD4WinBuilder.inf are correct. Don't worry about copying the file manually just rebuild and boot
The changes you made to UBCD4WinBuilder.inf are correct. Don't worry about copying the file manually just rebuild and boot
IT WORKED. Futzing paid off - and you folks who helped me were terrific.
FYI - I did not have to change the path to my XP folder as suggested. Some wonderful programmer was good enough to put things in quotes and it all worked fine.
My very great thanks
FYI - I did not have to change the path to my XP folder as suggested. Some wonderful programmer was good enough to put things in quotes and it all worked fine.
My very great thanks
QUOTE (pcuser @ Dec 16 2006, 06:26 PM)
Don't feel stupid!
The changes you made to UBCD4WinBuilder.inf are correct. Don't worry about copying the file manually just rebuild and boot
The changes you made to UBCD4WinBuilder.inf are correct. Don't worry about copying the file manually just rebuild and boot
EXCELLENT!!!
Good futzing job
Good futzing job
To save anyone else with a similar problem some (maybe a lot) of time I'll summarize what I learned to do IN ADDITION to the standard procedures.
1) Dell OEM disk are DIFFERENT - but they can be used with ubcd4win AFTER some steps
2) You have to download a file and create a "cmd" file to make the changes to address Dell's uniqueness. See:
http://www.ubcd4win.com/forum/index.php?showto...amp;#entry40122
3) You may get a Warning when running ubcd4win that MEGASAS.SYS is missing - If so:
- Find it on your Dell CD
- Copy it to your temporary directory - I put mine in the I386 files and it worked
- Modify the UBCD4WinBuilder.inf by inserting the following code: - I did it near the beginning and it worked fine.
megasas.sys=4,,4
These additional steps got me a working version of this amazing tool.
My thanks to all who helped along the way: Here's where all the back and forth is covered - view in outline mode.
http://www.ubcd4win.com/forum/index.php?showto...art=#entry40139
1) Dell OEM disk are DIFFERENT - but they can be used with ubcd4win AFTER some steps
2) You have to download a file and create a "cmd" file to make the changes to address Dell's uniqueness. See:
http://www.ubcd4win.com/forum/index.php?showto...amp;#entry40122
3) You may get a Warning when running ubcd4win that MEGASAS.SYS is missing - If so:
- Find it on your Dell CD
- Copy it to your temporary directory - I put mine in the I386 files and it worked
- Modify the UBCD4WinBuilder.inf by inserting the following code: - I did it near the beginning and it worked fine.
megasas.sys=4,,4
These additional steps got me a working version of this amazing tool.
My thanks to all who helped along the way: Here's where all the back and forth is covered - view in outline mode.
http://www.ubcd4win.com/forum/index.php?showto...art=#entry40139
QUOTE (AEngineer @ Dec 15 2006, 09:17 PM)
I have a new Dell Precision-390 Workstation (lovely machine - unbelievably quiet).
I tried to follow the instructions to create an ISO
- Downloaded ubcd4win v3.0 (first was shown 3.4 but totally different than web instructions)
- Copied my "Reinstallation CD" of XP-Pro with SP2 to a directory - had a checksum error in the DONTNETFX directory that I had to ignore after trying multiple times)
- Followed the creating instructions - including updating all the files for which that was possible
- Started the ISO creation and got the following messages (lots left out)
Help. What do I do now.
My thanks
Jim Mitchell
****************************
UBCD4Win PE Builder 3.1.10a
Copyright © 2004-2006 .
Running OS Version: 5.1.2600 (Service Pack 2)
Source product is: Windows XP Professional
CD-Rom name is: Windows XP Professional Service Pack 2 CD
Microsoft Product Code: 76487
Product channel ID is: OEM
Warning: building from an OEM version of Windows can mean trouble...
Source build: 2600
Build process started
Removing directory: C:\tmpC\ubcd4win30\BartPE
Removing existing hive files
Loading: C:\TMPC\UBCD4WIN30\BARTPE\I386\SYSTEM32\setuphiv
Error: loadKey() failed:
Processing INF file "C:\tmpC\ubcd4win30\UBCD4WinBuilder.inf"
Saving hive: C:\TMPC\UBCD4WIN30\BARTPE\I386\SYSTEM32\CONFIG\DEFAULT
Closing hive: C:\TMPC\UBCD4WIN30\BARTPE\I386\SYSTEM32\CONFIG\petmphive
Error: closeHive() failed: RegUnLoadKey (key="PEBuilder.exe-C:/TMPC/UBCD4WIN30/BARTPE/I386/SYSTEM32/CONFIG/petmphive") returned error 0: Access is denied.
Creating file: default.log
Creating file: software.log
Cleanup temporarily files
Error: DeleteFile() "C:\TMPC\UBCD4WIN30\BARTPE\I386\SYSTEM32\CONFIG\petmphive" failed
Error: DeleteFile() "C:\TMPC\UBCD4WIN30\BARTPE\I386\SYSTEM32\CONFIG\petmphive.log" failed
Error: DeleteFile() "C:\TMPC\UBCD4WIN30\BARTPE\I386\SYSTEM32\setuphiv" failed
Error: DeleteFile() "C:\TMPC\UBCD4WIN30\BARTPE\I386\SYSTEM32\setuphiv.log" failed
Collecting files
Processing INF file "D:\Temporary 390\XPCD\I386\layout.inf"
Processing OEM file: C:\tmpC\ubcd4win30\drivers\SCSIAdapter\VIA\sata_raid_ide_s\TXTSETUP.OEM
SCSI hardware ID: VIARAID_VT3149_XP, component: VIA Serial ATA RAID Controller(Windows XP)
Adding PnP ID: PCI\VEN_1106&DEV_3149
Processing OEM file: C:\tmpC\ubcd4win30\drivers\SCSIAdapter\Ximeta\ALL_NetDisk\txtsetup.oem
SCSI hardware ID: NetDisk_XP, component: WinXP Ximeta NetDisk Network Drives NDAS
Checking for missing files
Warning: File "megasas.sys" not found
Builder has stopped because there are 4 build errors
ISO image is not created, you must fix the errors!
Building done...
There where 4 errors and 2 warnings
I tried to follow the instructions to create an ISO
- Downloaded ubcd4win v3.0 (first was shown 3.4 but totally different than web instructions)
- Copied my "Reinstallation CD" of XP-Pro with SP2 to a directory - had a checksum error in the DONTNETFX directory that I had to ignore after trying multiple times)
- Followed the creating instructions - including updating all the files for which that was possible
- Started the ISO creation and got the following messages (lots left out)
Help. What do I do now.
My thanks
Jim Mitchell
****************************
UBCD4Win PE Builder 3.1.10a
Copyright © 2004-2006 .
Running OS Version: 5.1.2600 (Service Pack 2)
Source product is: Windows XP Professional
CD-Rom name is: Windows XP Professional Service Pack 2 CD
Microsoft Product Code: 76487
Product channel ID is: OEM
Warning: building from an OEM version of Windows can mean trouble...
Source build: 2600
Build process started
Removing directory: C:\tmpC\ubcd4win30\BartPE
Removing existing hive files
Loading: C:\TMPC\UBCD4WIN30\BARTPE\I386\SYSTEM32\setuphiv
Error: loadKey() failed:
Processing INF file "C:\tmpC\ubcd4win30\UBCD4WinBuilder.inf"
Saving hive: C:\TMPC\UBCD4WIN30\BARTPE\I386\SYSTEM32\CONFIG\DEFAULT
Closing hive: C:\TMPC\UBCD4WIN30\BARTPE\I386\SYSTEM32\CONFIG\petmphive
Error: closeHive() failed: RegUnLoadKey (key="PEBuilder.exe-C:/TMPC/UBCD4WIN30/BARTPE/I386/SYSTEM32/CONFIG/petmphive") returned error 0: Access is denied.
Creating file: default.log
Creating file: software.log
Cleanup temporarily files
Error: DeleteFile() "C:\TMPC\UBCD4WIN30\BARTPE\I386\SYSTEM32\CONFIG\petmphive" failed
Error: DeleteFile() "C:\TMPC\UBCD4WIN30\BARTPE\I386\SYSTEM32\CONFIG\petmphive.log" failed
Error: DeleteFile() "C:\TMPC\UBCD4WIN30\BARTPE\I386\SYSTEM32\setuphiv" failed
Error: DeleteFile() "C:\TMPC\UBCD4WIN30\BARTPE\I386\SYSTEM32\setuphiv.log" failed
Collecting files
Processing INF file "D:\Temporary 390\XPCD\I386\layout.inf"
Processing OEM file: C:\tmpC\ubcd4win30\drivers\SCSIAdapter\VIA\sata_raid_ide_s\TXTSETUP.OEM
SCSI hardware ID: VIARAID_VT3149_XP, component: VIA Serial ATA RAID Controller(Windows XP)
Adding PnP ID: PCI\VEN_1106&DEV_3149
Processing OEM file: C:\tmpC\ubcd4win30\drivers\SCSIAdapter\Ximeta\ALL_NetDisk\txtsetup.oem
SCSI hardware ID: NetDisk_XP, component: WinXP Ximeta NetDisk Network Drives NDAS
Checking for missing files
Warning: File "megasas.sys" not found
Builder has stopped because there are 4 build errors
ISO image is not created, you must fix the errors!
Building done...
There where 4 errors and 2 warnings
Congrats to AEngineer! 
@Joshua
@Joshua
QUOTE
What the hell is the meaning of : futz ???
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.