Jump to content











Photo
- - - - -

Strange Error


  • Please log in to reply
19 replies to this topic

#1 darkman738

darkman738

    Frequent Member

  • Advanced user
  • 134 posts
  • Location:MA, US
  •  
    United States

Posted 04 July 2008 - 03:12 AM

So I have a command line app that runs fine on a normal install of windows, but when I atempt to run in PE (Vista 1.2) I get this error:
"16-bit Windows Subsystem:
SYSTEM\CurrentControlSet\Control\VirtualDeviceDrivers\VDD. Virtual Device Driver format in the registry is invalid. Choose 'close' to terminate the application"
Not sure what this is, or why I recive it in PE only. I did find a site that stated to create the key in the registery, but I've checked on several computer I've ran it on that did not have this key. Also I atempted to create this key, but the application simply black screened then closed.

Any thoughts?

Thanks!

#2 Nuno Brito

Nuno Brito

    Platinum Member

  • .script developer
  • 10554 posts
  • Location:boot.wim
  • Interests:I'm just a quiet simple person with a very quiet simple life living one day at a time..
  •  
    European Union

Posted 04 July 2008 - 01:51 PM

You need to add support for 16 bit programs run under your 32 bit OS.

What is the program you trying to run?

For XP PE builds this has been solved some years ago, don't know if a similar script is available for VistaPE.

:)

#3 darkman738

darkman738

    Frequent Member

  • Advanced user
  • 134 posts
  • Location:MA, US
  •  
    United States

Posted 04 July 2008 - 02:40 PM

You need to add support for 16 bit programs run under your 32 bit OS.

What is the program you trying to run?

For XP PE builds this has been solved some years ago, don't know if a similar script is available for VistaPE.

:)


Its a virus command line scanner. OK, anyone have any idea how to do that?

#4 darkman738

darkman738

    Frequent Member

  • Advanced user
  • 134 posts
  • Location:MA, US
  •  
    United States

Posted 10 July 2008 - 07:15 AM

bump!

#5 darkman738

darkman738

    Frequent Member

  • Advanced user
  • 134 posts
  • Location:MA, US
  •  
    United States

Posted 10 July 2008 - 07:19 AM

Refferance
Straight from MS's site:

Because Windows on Windows (WOW) is not supported, 16-bit applications won’t run in 32-bit versions of Windows PE, and 32-bit applications won’t run in 64-bit versions of Windows PE.


PLEASE someone prove them wrong!

#6 Galapo

Galapo

    Platinum Member

  • .script developer
  • 3841 posts
  •  
    Australia

Posted 10 July 2008 - 10:37 AM

PLEASE someone prove them wrong!


http://livexp.boot-l...dos16bit.Script

#7 was_jaclaz

was_jaclaz

    Finder

  • Advanced user
  • 7100 posts
  • Location:Gone in the mist
  •  
    Italy

Posted 10 July 2008 - 03:09 PM

@Galapo

Actually the MS article refers to PE 2.x, i.e. Vista based, LiveXP AFAIK is PE 1.x-like i.e. XP based. :)

So the question posed by Nuno is still valid, as well as the one by darkman738.

If I get it right, the LiveXP .script you pointed to adds to the PE 1.x the so-called NTVDM:
http://support.micro...kb/314106/en-us
http://www.msfn.org/...hy-t118581.html


Does the same thing exist in Vista, and can it be added to VistaPE? :)


jaclaz

#8 missstefi

missstefi

    Newbie

  • Lady
  • 12 posts
  • Location:Franken
  •  
    Germany

Posted 10 July 2008 - 04:36 PM

So I have a command line app that runs fine on a normal install of windows, but when I atempt to run in PE (Vista 1.2) I get this error:
"16-bit Windows Subsystem:
SYSTEM\CurrentControlSet\Control\VirtualDeviceDrivers\VDD. Virtual Device Driver format in the registry is invalid. Choose 'close' to terminate the application"
Not sure what this is, or why I recive it in PE only. I did find a site that stated to create the key in the registery, but I've checked on several computer I've ran it on that did not have this key. Also I atempted to create this key, but the application simply black screened then closed.

Any thoughts?

Thanks!


Hi
try to use clampwin (portable app) virusscanner.
No registry entry´s needed. So you have only to integrat it in vista pe.

Steffi

#9 darkman738

darkman738

    Frequent Member

  • Advanced user
  • 134 posts
  • Location:MA, US
  •  
    United States

Posted 10 July 2008 - 06:21 PM

How do I get a set of files/directory to copy to the RamDisk (x:\ drive) when loading, inside the script? If I can do that, I might have ported it, but I can't be sure until I test it.

I should add I need these files to go to \Windows\ dir not program files. I have tried using:
RunFromRam,True

but it dosen't copy the files to the drive

#10 darkman738

darkman738

    Frequent Member

  • Advanced user
  • 134 posts
  • Location:MA, US
  •  
    United States

Posted 10 July 2008 - 06:29 PM

Hi
try to use clampwin (portable app) virusscanner.
No registry entry´s needed. So you have only to integrat it in vista pe.

Steffi


Hi, and thanks for the reply, but I'm not using clamwin, I'm using a command line scanner (several actually) and many of them were designed for pre-XP environment, but are still supported by the manufactures. CLS give the benefit of being able to automate a process, such that, I can have a program call several in succession to clean a computer. As no one scanner will remove all malware, a collection of the industry best is recommended. I have compiled a list of some of the best in the business, however most companies have abandoned CMD interface for GUI friendly versions to allow for a wider customer base(as CLS are commonly used by advanced users), and will not release a newer version that is not 16bit. The only exceptions are those that run on Linux units as many in the industry will use Linux servers for mail receiving, and CLS to scan incoming mail for viruses.

Thanks for the heads up!

#11 darkman738

darkman738

    Frequent Member

  • Advanced user
  • 134 posts
  • Location:MA, US
  •  
    United States

Posted 10 July 2008 - 09:44 PM

OK, I think I've got it. It will need some testing, but I think it's set. I'll post the .script file for you guys to take a look at, so that it can be edited as needed. I'm a horable scripter, and used a lot of differant sources for this. As of now, I haven't been able to sucessfuly add the files to the script, so for now the files will need to be in the %ScriptDir%\i386. I used the script that Galapo posted eirlier, and coppied as many files from a running x86 edition of Vista, then subed the rest with XP versions. Seems to work fine. Please let me know if you guys can help me edit this to include the files within the script, I can't seem to get it to work.

[codebox] [Main] Title=16 Bit support for VistaPE Selected=True Locked=True Description=This script will add support for DOS programs and windows applications in 16bit adding around 4Mb to your build. Author=John Adamopoulos; Darkman738 Contact=http://www.boot-land.net/forums Level=4 Updates=http://beta.boot-land.net Version=005 History005=Galapo added kb16.com to filelist, which provides support for non-US keyboards Date=2006-Okt-30 11:27:20 Upload=2007-May-04 17:52:34 [Process] Echo,"Copying Files..." If,NotExistDir,%TargetDir%\Windows,DirMake,%TargetDir%\Windows FileCopy,%ScriptDir%\i386\_default.pif,%TargetDir%\Windows FileCopy,%ScriptDir%\i386\kb16.com,%TargetDir%\Windows FileCopy,%ScriptDir%\i386\system.ini,%TargetDir%\Windows FileCopy,%ScriptDir%\i386\win.ini,%TargetDir%\Windows If,NotExistDir,%TargetDir%\Windows\System,DirMake,%TargetDir%\Windows\System FileCopy,%ScriptDir%\i386\System\avicap.dll,%TargetDir%\Windows\System FileCopy,%ScriptDir%\i386\System\avifile.dll,%TargetDir%\Windows\System FileCopy,%ScriptDir%\i386\System\commdlg.dll,%TargetDir%\Windows\System FileCopy,%ScriptDir%\i386\System\keyboard.drv,%TargetDir%\Windows\System FileCopy,%ScriptDir%\i386\System\lzexpand.dll,%TargetDir%\Windows\System FileCopy,%ScriptDir%\i386\System\mciavi.drv,%TargetDir%\Windows\System FileCopy,%ScriptDir%\i386\System\mciseq.drv,%TargetDir%\Windows\System FileCopy,%ScriptDir%\i386\System\mciwave.drv,%TargetDir%\Windows\System FileCopy,%ScriptDir%\i386\System\mmsystem.dll,%TargetDir%\Windows\System FileCopy,%ScriptDir%\i386\System\mouse.drv,%TargetDir%\Windows\System FileCopy,%ScriptDir%\i386\System\msvideo.dll,%TargetDir%\Windows\System FileCopy,%ScriptDir%\i386\System\olecli.dll,%TargetDir%\Windows\System FileCopy,%ScriptDir%\i386\System\olesvr.dll,%TargetDir%\Windows\System FileCopy,%ScriptDir%\i386\System\shell.dll,%TargetDir%\Windows\System FileCopy,%ScriptDir%\i386\System\stdole.tlb,%TargetDir%\Windows\System FileCopy,%ScriptDir%\i386\System\system.drv,%TargetDir%\Windows\System FileCopy,%ScriptDir%\i386\System\tapi.dll,%TargetDir%\Windows\System FileCopy,%ScriptDir%\i386\System\timer.drv,%TargetDir%\Windows\System FileCopy,%ScriptDir%\i386\System\vcdex.dll,%TargetDir%\Windows\System FileCopy,%ScriptDir%\i386\System\ver.dll,%TargetDir%\Windows\System FileCopy,%ScriptDir%\i386\System\vga.drv,%TargetDir%\Windows\System FileCopy,%ScriptDir%\i386\System\wfwnet.drv,%TargetDir%\Windows\System32 If,NotExistDir,%TargetDir%\Windows\System32,DirMake,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\ansi.sys,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\autoexec.nt,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\avicap32.dll,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\avifile.dll,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\command.com,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\commdlg.dll,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\compobj.dll,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\config.nt,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\country.sys,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\crtdll.dll,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\ctl3dv2.dll,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\ddeml.dll,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\dosx.exe,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\ega.cpi,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\gdi.exe,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\himem.sys,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\kb16.com,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\keyboard.drv,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\keyboard.sys,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\krnl386.exe,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\lanman.drv,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\MAPI.DLL,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\mciavi.drv,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\mciseq.drv,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\mciwave.drv,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\mmsystem.dll,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\mouse.drv,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\msacm.dll,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\mscdexnt.exe,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\msvideo.dll,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\netapi.dll,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\ntdos.sys,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\ntdos404.sys,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\ntdos411.sys,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\ntdos412.sys,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\ntdos804.sys,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\ntio.sys,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\ntio404.sys,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\ntio411.sys,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\ntio412.sys,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\ntio804.sys,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\ntvdm.exe,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\ntvdmd.dll,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\ole2.dll,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\ole2disp.dll,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\ole2nls.dll,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\olecli.dll,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\olesvr.dll,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\pmspl.dll,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\progman.exe,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\Rasapi16.dll,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\redir.exe,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\rtutils.dll,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\sfc.dll,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\sfc_os.dll,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\shell.dll,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\sound.drv,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\storage.dll,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\system.drv,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\timer.drv,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\toolhelp.dll,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\typelib.dll,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\user.exe,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\vcdex.dll,%TargetDir%\Windows\System32l FileCopy,%ScriptDir%\i386\System32\ver.dll,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\vga.drv,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\wfwnet.drv,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\win87em.dll,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\winoldap.mod,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\winspool.exe,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\wow32.dll,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\wowdeb.exe,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\wowexec.exe,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\wowfax.dll,%TargetDir%\Windows\System32 FileCopy,%ScriptDir%\i386\System32\wowfaxui.dll,%TargetDir%\Windows\System32 Echo,"Writing new values on registry hive.." Hive_Load,HKLM reg_add,0x2,"%reg%\ControlSet001\Control\WOW","cmdline","%SystemRoot%\system32\ntvdm.exe" reg_add,0x1,"%reg%\ControlSet001\Control\WOW","DefaultSeparateVDM","no" reg_add,0x1,"%reg%\ControlSet001\Control\WOW","LPT_timeout","15" reg_add,0x1,"%reg%\ControlSet001\Control\WOW","size","0" reg_add,0x1,"%reg%\ControlSet001\Control\WOW","wowsize","16" reg_add,0x2,"%reg%\ControlSet001\Control\WOW","wowcmdline","%SystemRoot%\system32\ntvdm.exe -a %SystemRoot%\system32\krnl386" reg_add,0x1,"%reg%\ControlSet001\Control\WOW","KnownDLLs","comm.drv commdlg.dll ctl3dv2.dll ddeml.dll keyboard.drv lanman.drv mmsystem.dll mouse.drv netapi.dll olecli.dll olesvr.dll pmspl.dll shell.dll sound.drv system.drv toolhelp.dll vga.drv wfwnet.drv win87em.dll winoldap.mod winsock.dll winspool.exe wowdeb.exe timer.drv rasapi16.dll compobj.dll storage.dll ole2.dll ole2disp.dll ole2nls.dll typelib.dll msvideo.dll avifile.dll msacm.dll mciavi.drv mciseq.drv mciwave.drv progman.exe avicap.dll mapi.dll command.com kb16.com rtutils.dll sfc.dll sfc_os.dll" reg_add,0x4,"%reg%\ControlSet001\Control\WOW","SharedWowTimeout","0x00000e10" reg_add,0x3,"%reg%\ControlSet001\Control\WOW","RomFontPointers","b0,52,00,c0,b0,4a,00,c0,b0,4e,00,c0,b0,60,00,c0,c0,60,00,c0,c0,70,00,c0" reg_add,0x1,"%reg%\ControlSet001\Control\Session Manager\Environment","PATHEXT",".COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH" reg_add,0x7,"%reg%\ControlSet001\Control\VirtualDeviceDrivers","VDD","" Hive_Unload,HKLM [Interface] pTextLabel1="This script is needed whenever you wish to add 16bit DOS or Windows programs on your build.",1,1,21,16,285,51,8,Normal
pWebLabel1="Support topic",1,10,210,49,84,18,http://www.boot-land.net/forums/index.php?showtopic=151
pWebLabel2="What is a 16bit program?",1,10,43,102,165,18,http://en.wikipedia.org/wiki/16-bit_application
[/codebox]

edited to include sfc.dll and sfc_os.dll.
Edited atachment to only include script file. Sorry, for now you will need to track down each file individualy, or throw into editpad and find/replace and coppy from a good install of Vista.

Good Luck, I'll be atempting to get this to work from the source disk, but unfortunatly, if the files are there, they seem to be encoded some other way... its not looking good.

Attached Files



#12 Galapo

Galapo

    Platinum Member

  • .script developer
  • 3841 posts
  •  
    Australia

Posted 10 July 2008 - 10:54 PM

Actually the MS article refers to PE 2.x, i.e. Vista based, LiveXP AFAIK is PE 1.x-like i.e. XP based.

I stand corrected (I admit I didn't read the article!). darkman738 might be able to answer the question hopefully:

Does the same thing exist in Vista, and can it be added to VistaPE? :)


@darkman738
Sorry, I can't encode the files in the script to distribute as they're non-redistributable MS files.

Regards,
Galapo.

#13 JonF

JonF

    Gold Member

  • .script developer
  • 1185 posts
  • Location:Boston, MA
  •  
    United States

Posted 10 July 2008 - 11:41 PM

How do I get a set of files/directory to copy to the RamDisk (x:\ drive) when loading, inside the script? If I can do that, I might have ported it, but I can't be sure until I test it.

Write a .cmd file and point your shortcuts to it. See my Ad-Aware and Spybot scripts in the download center for examples.

I should add I need these files to go to \Windows\ dir not program files.

That seems awfully strange ... if they're in SystemRoot (which is writable in VistaPE, up to a limit ... default 64 MB) why copy them to RAMdisk? But ...

unpack,<Folder>,,,%target_win%

#14 darkman738

darkman738

    Frequent Member

  • Advanced user
  • 134 posts
  • Location:MA, US
  •  
    United States

Posted 11 July 2008 - 12:11 AM

I stand corrected (I admit I didn't read the article!). darkman738 might be able to answer the question hopefully:


@darkman738
Sorry, I can't encode the files in the script to distribute as they're non-redistributable MS files.

Regards,
Galapo.


OK, I'll check to see if I can mod this to work from the source directory rather than a folder. If they exist on the disk... Some of these files did not exist on the Vista unit, which may mean they are not needed, I am unsure, but for now, it seems, everything is working OK, so we'll work from here.

Should I remove the .7z file? It contains the files necessary.

#15 darkman738

darkman738

    Frequent Member

  • Advanced user
  • 134 posts
  • Location:MA, US
  •  
    United States

Posted 11 July 2008 - 12:20 AM

Write a .cmd file and point your shortcuts to it. See my Ad-Aware and Spybot scripts in the download center for examples.


That seems awfully strange ... if they're in SystemRoot (which is writable in VistaPE, up to a limit ... default 64 MB) why copy them to RAMdisk? But ...

unpack,<Folder>,,,%target_win%


I got it to work. Turns out that if you place the files in the %TargetDir%\Windows\ it gets packaged and extracted on boot. That seemed to solve my problem. Thanks

#16 Galapo

Galapo

    Platinum Member

  • .script developer
  • 3841 posts
  •  
    Australia

Posted 11 July 2008 - 12:21 AM

Should I remove the .7z file? It contains the files necessary.

Yes, I think so: we don't want trouble with MS.

Regards,
Galapo.

#17 darkman738

darkman738

    Frequent Member

  • Advanced user
  • 134 posts
  • Location:MA, US
  •  
    United States

Posted 13 July 2008 - 12:20 AM

I have atached a bat file that shold collect the key files into the %SystemDrive%\backup (normaly c:\backup). I'd recommended running the bat file from command prompt with the command:

generate.bat > LogFile.txt

This will give you a list of any files it can't copy. Also this should be ran on a x86 (thats 32bit version) of Windows Vista NOT x64. x64 versions of Vista do not support 16bit DOS (accourding to an article from their site.) If you run with this, you can google any files not coppied. You may also check a Windows XP install for missing files (agin 32bit ONLY) to fill in the blanks should you have a hard time finding some files online.
Once ran, you will need to move/copy the folder %SystemDrive%\backup to the %ScriptPath% directory and rename it to i386. That should be all, sorry I can't make it easier.
As of right now, I have to way of pulling these files off a Vista Installation Disk, should anyone care to try I'd apreciate it, I cant find them!

A couple of people have informed me that there are some files that may not be necessary... This may be true, and if anyone would like to trim the list, thats fine. This is the most comprehensive list I could compile for my uses, and was adapted from a XP Live script. The only files I've added were "sfc.dll" and "sfc_os.dll" which are necessary for quite a few programs that directly access files (such as command line virus scanners.)

Let me know if you have any sugestions. I will post a more user friendly version wen

Attached Files



#18 darkman738

darkman738

    Frequent Member

  • Advanced user
  • 134 posts
  • Location:MA, US
  •  
    United States

Posted 19 July 2008 - 04:22 AM

Ok, so I accadenly found where the files are located on the install disk. Does Winbuilder support extracting files from a .wim file? Then I can test if all files necessary are present on the install DVD.

Thanks

#19 Galapo

Galapo

    Platinum Member

  • .script developer
  • 3841 posts
  •  
    Australia

Posted 19 July 2008 - 05:00 AM

Does Winbuilder support extracting files from a .wim file?


WinBuilder itself doesn't, but since new 7zip can extract from WIM images, you should be able to get the files you're after without needing WAIK files.

Regards,
Galapo.

#20 Nuno Brito

Nuno Brito

    Platinum Member

  • .script developer
  • 10554 posts
  • Location:boot.wim
  • Interests:I'm just a quiet simple person with a very quiet simple life living one day at a time..
  •  
    European Union

Posted 19 July 2008 - 10:29 AM

Sorry, I can't encode the files in the script to distribute as they're non-redistributable MS files.


Anyone willing to check if ReactOS or Wine contain the required DLL files?

ROS: http://www.reactos.org/getbuilds/

Wine: http://sourceforge.n...ckage_id=112520

This might be a solution to overcome MS restrictions.

:cheers:




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users