![]() |
![]() | ![]() | ![]() | ![]() | ![]() | ![]() | ![]() |
| Welcome to Windows Vista Forums. Our forum is dedicated to helping you find solutions with any problems, errors or issues you are experiencing with Windows Vista. The Vista forum also covers news and updates and has an extensive Windows Vista tutorial section that covers a wide range of tips and tricks. |
| |||||||
![]() |
| |
| | #1 (permalink) |
| | 32 bits 64 bits Hi, I a 32 bytes version the same as a 64 bits version of wscript? I have wscript 7.7.0.18068 on Vista 64. Set oJcb=WScript.CreateObject("jcb.tools", "event_") Iget: Cant find jcb.tools code 80040154 WScript.Create Object Thanks, Jean Pierre Daviau ------- HP Pavilion Elite m9525f Desktop PC Vista Édition Familiale Premium SP1 64 bits |
My System Specs![]() |
| | #2 (permalink) |
| | Re: 32 bits 64 bits It IS the same, BUT - you cannot run a 32-bit DLL inside a 64-bit process or a 64-bit DLL inside a 32-bit process. If there is no 64-bit version of the DLL containing jcb.tools, you should explicitly run scripts depending on it from the 32-bit version of WSH. It's located at C:\Windows\Syswow64\wscript.exe or C:\Windows\Syswow64\cscript.exe. "Jean Pierre Daviau" <onceWasenough@xxxxxx> wrote in message news:eM7wxAOoJHA.1288@xxxxxx Quote: > Hi, > > I a 32 bytes version the same as a 64 bits version of wscript? > > I have wscript 7.7.0.18068 on Vista 64. > > Set oJcb=WScript.CreateObject("jcb.tools", "event_") > > Iget: > Cant find jcb.tools > code 80040154 > WScript.Create Object > > Thanks, > > > Jean Pierre Daviau > > ------- > HP Pavilion Elite m9525f Desktop PC > Vista Édition Familiale Premium SP1 64 bits > |
My System Specs![]() |
| | #3 (permalink) |
| | Re: 32 bits 64 bits Ok. Quote: > C:\Windows\Syswow64\wscript.exe or C:\Windows\Syswow64\cscript.exe. Now. I have bought Tobias Weltner Windows® Scripting Secrets® (32 bit version probably. If I try to run a set up , I get invalid command line prompt. .. Where should I install (in system32? subdirectory? ) .dl_, .oc_, .tl_ files. . . . ? ---- ---- M:\UNZIPW-SCRIPTING\WINDOWSSCRIPTINGSECRETS\CODE\INSTALL\ICONHANDLER AsycFilt.dl_ ComCat.dl_ Ctl3d32.dl_ iconhandler.oc_ MsStkPrp.dl_ MSVBVM50.dl_ OleAut32.dl_ olepro32.dl_ SETUP.EXE SETUP.LST SETUP1.EX_ ST5UNST.EX_ StdOle2.tl_ VB5StKit.dl_ ------------------------------------------- "Alex K. Angelopoulos" <aka(at)mvps.org> a écrit dans le message de news:%238pc2aOoJHA.5100@xxxxxx Quote: > It IS the same, BUT - you cannot run a 32-bit DLL inside a 64-bit process > or a 64-bit DLL inside a 32-bit process. If there is no 64-bit version of > the DLL containing jcb.tools, you should explicitly run scripts depending > on it from the 32-bit version of WSH. It's located at Quote: > "Jean Pierre Daviau" <onceWasenough@xxxxxx> wrote in message > news:eM7wxAOoJHA.1288@xxxxxx Quote: >> Hi, >> >> I a 32 bytes version the same as a 64 bits version of wscript? >> >> I have wscript 7.7.0.18068 on Vista 64. >> >> Set oJcb=WScript.CreateObject("jcb.tools", "event_") >> >> Iget: >> Cant find jcb.tools >> code 80040154 >> WScript.Create Object >> >> Thanks, >> >> >> Jean Pierre Daviau >> >> ------- >> HP Pavilion Elite m9525f Desktop PC >> Vista Édition Familiale Premium SP1 64 bits >> |
My System Specs![]() |
| | #4 (permalink) |
| | Re: 32 bits 64 bits And these? ..lib, .ocx, .vbp, .vbw, .bas, .exp How can I register them in the register? Quote: > ---------------------------------- > M:\UNZIPW-SCRIPTING\WINDOWSSCRIPTINGSECRETS\CODE\COMPONENTS\WINMANAGER > winmanag.exp > winmanag.lib > winmanag.ocx > winmanager.bas > winmanager.ctl > winmanager.vbp > winmanager.vbw > ------------------------------------- |
My System Specs![]() |
| | #5 (permalink) |
| | Re: 32 bits 64 bits On Mon, 09 Mar 2009 20:01:22 GMT, Jean Pierre Daviau wrote: Quote: > And these? > .lib, .ocx, .vbp, .vbw, .bas, .exp > > How can I register them in the register? Quote: >> ---------------------------------- >> M:\UNZIPW-SCRIPTING\WINDOWSSCRIPTINGSECRETS\CODE\COMPONENTS\WINMANAGER >> winmanag.exp probably don't need it. Quote: Quote: >> winmanag.lib them. If you don't know what that means, you probably don't need it. Quote: Quote: >> winmanag.ocx regsvr32 winmanag.ocx (Assuming that regsvr32 even exists on Win64. YMMV.) Quote: Quote: >> winmanager.bas >> winmanager.ctl >> winmanager.vbp >> winmanager.vbw for using the OCX. You *probably* don't need them, although it wouldn't hurt to look through them. Most of the files listed in your previous post (*.??_) are compressed. To install them, I'd suggest running SETUP.EXE. If setup doesn't work, you can try manually expanding everything from the command line: expand -r *.??_ ....although you probably only need to worry about iconhandler.oc_, since everything else looks to be either part of the installer or updates for old systems. Once it's expanded, register with regsvr32: regsvr32 iconhandler.ocx -- auric dot auric at gmail dot com -- You know it's been a long day when "this morning" feels like "yesterday". |
My System Specs![]() |
| | #6 (permalink) |
| | Re: 32 bits 64 bits > This is an ActiveX control, most likely 32-bit code. Register like this: regsvr32 winmanag.ocx Quote: > > (Assuming that regsvr32 even exists on Win64. YMMV.) Quote: > Most of the files listed in your previous post (*.??_) are compressed. To > install them, I'd suggest running SETUP.EXE. If setup doesn't work, you > can > try manually expanding everything from the command line: > expand -r *.??_ /? . I only see the -r -D -F Quote: > ...although you probably only need to worry about iconhandler.oc_, since > everything else looks to be either part of the installer or updates for > old > systems. Once it's expanded, register with regsvr32: I putted them in system32 and registered them there I putted them in syswow32 and registered them there Nothing worked Can I create syswow32 \wsh and registered them there? |
My System Specs![]() |
| | #7 (permalink) |
| | Re: 32 bits 64 bits Quote: > Can I create syswow32 \wsh and registered them there? It seems I registered some successfully |
My System Specs![]() |
| | #8 (permalink) |
| | Re: 32 bits 64 bits <WSeincdreotwss® Scripting ® <Tobias Weltner <Windows® Scripting Secrets® I have registered them there and some scripts works. C:\WINDOWS\SYSWOW64\WSH | comcat.dl | comctl32.oc | COMCTL32.OCX | iconhandler.oc | iconhandler.ocx | jcb.ocx | listview.oc | modeless.oc | msstkprp.dl | msvbvm50.dl | msvbvm50.dll | oleaut32.dl | olepro32.dl | stdole2.tl ------------------------------------------------------ The script runs a progressing bar shows while it scans the c: drive the iconlist.txt is created then Line 77 caracter 6 unknown path Code 800a004c Ctrl c and the scipt stops. I kill the remaining process in task manager. ==================================== 22-2.VBS =================================================== 1 ' 22-2.VBS 2 ' for %i in (22*.vbs) do ( C:\Windows\Syswow64\wscript.exe\%i & pause) 3 ' for %i in (*) do (regsvr32 "C:\Windows\SysWOW64\wsh\%i" & pause) 4 ' regserv32 C:\Windows\SysWOW64\wsh\iconhandler.ocx 5 '---the following lines have been added to ensure all required COM objects are available on your system. 6 ' script uses the following components: 7 ' icon.handler 8 ' scripting.filesystemobject 9 ' wscript.shell 10 ' modeless.dialog 11 12 CheckCOM 13 '---end of COM-object checking code--- 14 15 16 set tool = CreateObject("icon.handler") 17 set fs = CreateObject("Scripting.FileSystemObject") 18 set wshshell = CreateObject("WScript.Shell") 19 set dlg = WScript.CreateObject("modeless.dialog", "event_") 20 21 ' define variables: 22 iconlist = "C:\Users\Jean Pierre\Desktop\iconlist.txt" 23 list = "" 24 quit = false 25 iconfilecount = 0 26 icons = 0 27 28 ' open icon list file 29 set list = fs.CreateTextFile(iconlist, true) 30 31 ' show modal window 32 ' everything else is handled by event_WakeUp 33 dlg.ShowProgressDialog 34 35 ' close file 36 list.close 37 38 wshshell.run """" & iconlist & """" 39 40 sub event_WakeUp 41 ' will be executed the moment your modal dialog becomes visible 42 ' search all local hard drives 43 for each drive in fs.Drives 44 if quit then 45 ' make sure to display this message! 46 ' otherwise your script won't find back to the 47 ' starting process! 48 wshshell.Popup "Interrupted search...", 1 49 dlg.CloseDialog 50 exit sub 51 end if 52 if drive.isReady and drive.DriveType=2 then 53 SearchFolder drive.RootFolder 54 end if 55 next 56 57 ' make sure to display this message! 58 ' otherwise your script won't find back to the 59 ' starting process! 60 61 wshshell.Popup "Done!", 1 62 dlg.CloseDialog 63 end sub 64 65 sub event_QuitNow 66 quit = true 67 end sub 68 69 70 sub SearchFolder(folderobj) 71 ' don't search recycle bin 72 if lcase(folderobj.name) = "recycled" then exit sub 73 if lcase(folderobj.name) = "dllcache" then exit sub 74 75 ' search for icons and create list 76 counter = 0 77 filecount = folderobj.files.count 78 drv = folderobj.Drive.Driveletter 79 80 for each file in folderobj.files 81 if quit then exit sub 82 83 counter = counter +1 84 percent = Fix(counter * 100/filecount) 85 86 dlg.WriteDialog "Scanning Drive " & drv & vbCr _ 87 & vbCr & folderobj.path & vbCr & file.name _ 88 & vbCr & "found " & iconfilecount _ 89 & " icon files and " & icons & " icons." 90 dlg.SetProgress percent 91 92 dlg.HandleEvent 93 ' number of icons stored in file: 94 iconcount = tool.GetIconNumber(file.path) 95 96 if iconcount>2 then 97 iconfilecount = iconfilecount + 1 98 icons = icons + iconcount 99 list.WriteLine iconcount & vbTab & file.path 100 end if 101 next 102 for each subfolder in folderobj.subfolders 103 if quit then exit sub 104 SearchFolder subfolder 105 next 106 end sub 107 108 109 ' --- the following code had been automatically added to ensure all required COM objects are installed. 110 function COMExists(name) 111 ' checks whether a specific COM object is installed on 112 ' your local machine 113 set cwsh = CreateObject("WScript.Shell") 114 on error resume next 115 dummy = cwsh.RegRead("HKCR\" & name & "\") 116 if err.number<>0 then 117 COMExists = false 118 else 119 COMExists = true 120 end if 121 end function 122 123 sub CheckCOM 124 if not COMExists("icon.handler") then 125 msg="COM-Object ""icon.handler"" is required. This object is currently not installed on your system." & vbCr 126 msg = msg & "Install the ICONHANDLER component from CD" & vbCr 127 MsgBox msg, vbExclamation 128 129 end if 130 131 if not COMExists("scripting.filesystemobject") then 132 msg="COM-Object ""scripting.filesystemobject"" is required. This object is currently not installed on your system." & vbCr 133 msg = msg & "Reinstall the Windows Scripting Host!" & vbCr 134 MsgBox msg, vbExclamation 135 136 end if 137 138 if not COMExists("wscript.shell") then 139 msg="COM-Object ""wscript.shell"" is required. This object is currently not installed on your system." & vbCr 140 msg = msg & "Reinstall the Windows Scripting Host!" & vbCr 141 MsgBox msg, vbExclamation 142 143 end if 144 145 if not COMExists("modeless.dialog") then 146 msg="COM-Object ""modeless.dialog"" is required. This object is currently not installed on your system." & vbCr 147 msg = msg & "Install the MODELESS component from CD" & vbCr 148 MsgBox msg, vbExclamation 149 150 end if 151 152 end sub 153 '--- end of COM object checking code 154 155 ' (C) 2000 by Dr. T. Weltner - all rights reserved. 156 --------------------------------- 2-2-.vbs ------------------------------ |
My System Specs![]() |
![]() |
| Thread Tools | |
| |
Similar Threads | ||||
| Thread | Forum | |||
| Need help in 32 bits to 64 bits switching... | General Discussion | |||
| Vista 32 bits to Vista 64 bits without loosing apps. | Vista installation & setup | |||
| Internet Explorer 7 (32-bits) keeps on freezing wile the 64-bits works OK in Vista 64 | Vista General | |||
| Why does x86 mean 64 bits while x32 means 32 bits? | Vista General | |||
| BITS | Vista installation & setup | |||