Cisco Blog

Awesome! I was just about to set up CM on an old box myself.

Sean

Good. Can it run on MS Win2K or must be MS Win2K Advanced Server

It runs on Windows 2K standard (non-advanced server), which is what the CallManager image is designed for.

Awesome hint - I tried to do something like this a year or so ago, but couldn't get it to work immediately, and gave up too quick...

I couldn't get this model to work on MS Virtual PC - I think it was having trouble with the RAID adapter.. So, I used:

SET XIMAGE=7815
goto IBM7815

That seems to work on the VPC image...

Thanks!
-Steve

Spoke too soon - Image loaded fine on VPC, but hangs on "Starting Windows".. Even in safe mode. Back to the drawing board.. Anyone else trying to get this to work on VPC/Virtual Server?

OK.. Maybe this will work for VPC!! :-)
set XIMAGE=7830
goto CPQ7830

It loaded (from disk 7) and is currently actually booted up, and "writing system configuration" so I think it's going to work! Sorry for the confusion / bad info on the VPC...

Excellent - thanks Steve for testing it out!

Is there anyway to get around the 1 GB RAM check when installing CallManager 4.1(3) and later? None of the registry hacks work for this check. I extracted the config files in the installer and tried editing them but didn't work. The unsupported machine with 512MB I'm using let me install 4.1(2), but the 4.1(3) install required 1GB of RAM.

Thanks,
Kevin

I managed to get a CM working on a generic PC with the instructions from the very first post. Mine too failed to re-boot, but then after turning it off and on several times it started the instalation again and I had no problems after that. It does however seam un-reliable. Needs re-booting several time a week due to services just stopping such as the CM TFTP service etc. I only use it in a lab environment to test so this isn't too big an issue. Anybody had similar experiences?

Does anybody have a copy of the latest CM?

I'm trying to install CCM 4.1(2) natively on VMware using the hardware detection CDs. The floppy technique as described above works until the point when the system returns an unable to detect raid controller error.

Does anyone have any suggestions for a workaround?

Thanks,
Eric

First, thanks for the post. I've successfully loaded CCM on other machines using the reg hack, but they were never stable enough to even test with. But this way seems to be working so far. I've gotten it to work on a Dell Optiplex 520. I did have to make some changes though. I was getting caught up with the raid drives as Eric was.

Further down in the BAt file find the line ":IBMX345" the line below it calls batch file that determines the raid driver needed. Comment out that line by adding "REM". Worked for me.

Rich

All,

Does it matter what type of hardware? Like for example Dell GX240 with just a single HDD, non-SCSI?

Tim - The GX240 was actually the test machine I used to pull this off. It works great ;).

I see. I am not sure then what I might be doing wrong with the instructions...basically I am stuck on step 9, I never really see a "wizard". I do get to where the Cisco Assisted Install screen comes up, it says it could not find any disk or server information...I hit next and the pc re-boots and starts the process over again. I tried changing autoexec from x345, to x330 with slightly different results as far as "server/disk" info, but after that re-boot, it starts the process over again...

PANICKED!! Sorry, I was able to get it to work when I changed the autoexec to 7820. However, now it asks for disk 5?? Anyway, I will keep plugging away at it. (My cd set does not have a disk 5 - go figure) lol

Ok...got it to work. My earlier posts were from me trying to install IP Telephony Server - OS Version 2000 2.4. However, I now realize, the instructions above work with OS Version 2000 2.7a CD set. All is good! Thanks for the information!

Was the driver of the machine you were installing to blank, or did it already have an OS installed... I seem to hang each time after it says Please Wait While the Assisted Install loads...

When I try : c:\fdimage k:\bootimg.bin a:
I always get the message : k:\bootimage.bin - No such file or directory

any suggestions, please?

Many thanks for this, I have created the floppy boot disk as described but looking on the floppy there is no autoexex.bat, could you tell me what I need to put in the file along with set XIMAGE=x345
goto IBMx345

Regards

Sorted the above out, is there a way to install on a none raid system?

Hi Martyn,

can you please send the diskimage to me? mike.leske@gmail.com

thanks in advance.
mike

A couple things - First, That's great info on stopping it from checking on the raid hardware. Thanks Eric!

Second - The OS install disks I used to test this are 2000.2.4 disks, which I then upgrade to the latest by the standard upgrade patches from Cisco.com. I have installed from these disks on MS Virtual PC, and a generic Athlon 64 machine I just built, which had a single 80 gig IDE drive in it (so yes, you can do it without a raid).

Keep in mind, theres a bunch of OS images - Cisco built one for each type of hardware the software is SUPPOSED to run on. Depending on what hardware you choose (ie, which "set" and "goto" you add into the autoexec.bat), it will tell you to insert the right CD (or DVD in the case of some of the disks, like disk 3 in my set).

The biggest trick is to find (by trial and error) an image that has a disk controller driver installed that is at least minimally compatible with the hardware you have, or at the very least, will allow it to boot, so that you can install the proper driver. In my case, during the first boot, it found several hardware devices (sound card, video adapter, game port, etc) that didn't have drivers loaded in the original image from the Cisco CDs. I just kept clicking "cancel" as quick as I could, so that the image load process would continue. After the image was loaded, and I could log into the machine, I loaded my drivers.

One other hint - I found that my load would fail if I didn't have power management enabled in the bios. I dont know if this is a definite, but it seemed consistent to me. All I can say is try all the installs 'till you get one working..

Anyone got a hint for getting one working on VMWare? I've done VPC, but I haven't tried VMWARE yet, and I need to do so soon...

Thanks, and good luck!
-Steve

One more thing - Someone mentioned not being able to find the disk image - Keep in mind that this process will presumably only work with a disk set that was sold as a "software only" install of CCM. If you buy the MCS hardware with call manager software, they usually send you the exact version (and only the one version) of software that works with that hardware, which usually comes on two disks, as opposed to the 14 or so disks that I have in my set.

Just thought I'd mention it..

Can you post you autoexec so I can compare with mine, I can not stop it searching for a Raid

Martyn

No worries I sorted the autoexec out, I have read on other sites that you need to load the Cisco win-os upgrades, does that need to be done or can it be left out

Martyn

I'm having the same problem as Steve had, windows starts to load but then hangs at the starting windows screen and I can not even boot into safe mode

Any Ideas anyone

Martyn

Thanks much for the info JC ... I just used your instructions to install on a RAID based Compaq DL320 by telling it to load as a DL380. (The Cisco build for the DL320 doesn't load the SCSI drivers)

Spoke too soon ... after the install, and during Win2K bootup, I get the BSOD with INACCESSIBLE_BOOT_DEVICE ... My goal is to install CCM 4.1(3) on a DL320 with SCSI/RAID drives instead of the IDE setup which Cisco typically installs based on the 7825 platform. I switched the autoexec.bat to load the 7835H03 image, though I got the same thing.

Any suggestions? Thanks,

joe

I have an MCS 7800 and I want to put a Publisher and Subscriber on one machine. I took a class a few weeks ago where they did this and I can't figure it out. I've installed VMware Server on the MCS 7800 and start a new virtual server. I boot it up with the hardware detection cd and it fails, saying the OS does not support this hardware. Any ideas on how to get both installed?

Thanks

I managed to get 4.12 working on VIA ITX 800Mhz - very small and neat. It took me about 2 weeks of hacking but it was worth it. It's solid as a rock - I have had it running for over 6 months without a reboot. I also have Unity running on a seperate ITX machine. This hack was truly a nightmare - hacked for 2 weeks 12 hour days. Both are totally stable.
It can be done!

I got this to work on a Compaq DL360 (2x933/SCSI RAID, 512 RAM, very similar to a DL320 above) using the 7825HO option in autoexec.bat.

Upon initial bootup, I got the BSOD with the inaccessible boot device error. To correct this, I had to boot to the W2KSP4 CD, choose "Enter" (just like a fresh install) & then choose "Repair" when it finds the installation on the logical drive. After going through that process & it's many reboots it seems to be fine.

I upgraded to the latest OS service pack & installed CCM & all related patches.

I've had this running for a little over a week with no issues. All in all this was a really ugly way to do it, but it worked for me...YMMV.

Hope it helps.

Hi I am stuggling to get this done I am have a acompaq DL360 Server and I cant get it work.
I have dowloaded the fdimage.exe on browsing the dvd disk1 I cant see the bootimg.bin file so I cant create the floppy disk.

I am trying to install 4.2(3)

Any help will be appreciated

Thanks

Version 4.1(3)

Harry,

Why do you not share your files with all of us?

Posted by: Harry at September 28, 2006 4:20 PM

I managed to get 4.12 working on VIA ITX 800Mhz - very small and neat. It took me about 2 weeks of hacking but it was worth it. It's solid as a rock - I have had it running for over 6 months without a reboot. I also have Unity running on a seperate ITX machine. This hack was truly a nightmare - hacked for 2 weeks 12 hour days. Both are totally stable.
It can be done!

In fact, I think JC (June 14th post) originally sharing the information and starting this thread is FANTASTIC!

It would be great if everyone shared what they have been doing so we can all benefit from the knowledge.
This way, we all know what works and what does not work.
We could gain some good metrics on pairing white box hardware and/or virtual machines (Microsoft, VMware, XenSource) with the HP or IBM hardware in the autoexec.bat.

Remember the 90/10 rule.

90 percent of a group will consume what 10 percent contribute/create.

JC gave us a great contribution.
Let us all share what we have discovered through our tinkering and build on what he has given us.

Just my 5 cents. :-)

Warmest wishes and very best regards to all.

Hi all,

like Bill and Scott, I too have the DVD disk without the bootimg.bin file. Is there any way to accomplish this trick?

Thanks a lot!

Hi everybody,

to get the bin file I've found out bbie http://www.nu2.nu/bbie/ that allows to extract any boot sector from cd or dvd. I've tried with my dvd ccm 4.2 and apparently it gets an img file out of it.

Now my question, how do you build the boot floppy. I've tried multiple sites with descriptions and utilities to create boot floppies but just does not fit regarding the autoexec.bat and the lines that need to be modified.

Thanks

Xav

FYI - I stumbled across a site giving instructions on installing Cisco CallManager 4.x in VMWare:

http://www.knuckledragger.net/Network/ccm4vmware.htm

hi JC and other friends,
Would you pls help me?
thanks a lot!
When I run step 9,it always display the following
info then shutdown:
Cannot find System.ini.
You need to run Windows Setup again to install the file

Dear all,
i use OS Version 2000 2.7a hardware detection CD ,after run "fdimage d:\bootimg.bin a:",I got file autoexec.bat:

@ECHO OFF

REM
REM Cisco MCS Build Process Boot-CD #1
REM
REM Last Modified On: 12/10/2004
REM
REM version: 1036 (move ServeRAID driver and config off this diskette)
REM version: 1035 (Added X346NoHT.exe to disable HTT on X346)
REM version: 1034 (IBM X345 using different ServeRAID firmware)
REM version: 1033 (Added support for 7835H04, 7835I02, 7845H03, 7845I02)
REM version: 1032 (Switched to new IBM hwdetect.exe and clini.exe utils)
REM version: 1031 (Updated for OS 2000.2.6)
REM version: 1030 (Added support for ServeRAID 6i and 7845I01)
REM version: 1029 (Added 7815I-2, 7825H-2, 7835H-3, 7845H-2 detection)
REM version: 1028 (removed unused files)
REM version: 1027 (Added support for X345, 867031X)
REM version: 1026 (Added support for model # 84793AX for 7815)
REM version: 1025 (Added support for Proliant 400 same as PS-720)
REM version: 1024 (Added partinfo back for X330's and sticfg for X330 -11Y detection)
REM version: 1023 (Added support for 7845)
REM version: 1022 (Changed partinfo to fdisk for x200 support)
REM version: 1021 (1018 and 1019 were not provided by Spirian. Added in 783G support)
REM version: 1020 (Added support for x200 changed all detection) eburgess
REM Version: 1017 (Added support for X342 and X33A)
REM Version: 1016 (Skips PCICFG on X340)
REM Version: 1015 (Added support for ServeRAID controller 4Lx)
REM Version: 1014 (removed MCS references)
REM Version: 1013 (IBM RAID Firmware Update Support2)

cls
set CDROM=S
set EXPAND=YES
SET DIRCMD=/O:N
set LglDrv=27 * 26 Z 25 Y 24 X 23 W 22 V 21 U 20 T 19 S 18 R 17 Q 16 P 15
set LglDrv=%LglDrv% O 14 N 13 M 12 L 11 K 10 J 9 I 8 H 7 G 6 F 5 E 4 D 3 C

echo PLEASE WAIT AS BOOT PROCESS COMPLETES

call setramd.bat %LglDrv%

set LglDrv=
set CDROM=S
set EXPAND=YES
set temp=%RAMD%:\
path=%RAMD%:\;a:\;%CDROM%:\;s:\win95;s:\win95\system;%RAMD%:\extract;

%RAMD%:
md encrpt
md win95
md Extract

copy s:\win95\*.dat %RAMD%:\win95\*.*
copy s:\win95\*.da0 %RAMD%:\win95\*.*
copy s:\win95\MCSboot.exe %RAMD%:\win95\*.*
copy s:\win95\mscom*.ocx %RAMD%:\win95\*.*
rem unrem the following for testing and put your MCSboot.exe on the a: disk
rem copy a:\mcsboot.exe %RAMD%:\win95\*.*
copy s:\win95\*.ini %RAMD%:\win95\*.*
copy s:\win95\eula.txt %RAMD%:\win95\eula.txt
copy s:\win95\ciscoe.txt %RAMD%:\win95\ciscoe.txt
copy s:\tools\wait4cd.bat %RAMD%:\wait4cd.bat
copy s:\tools\waitcd.exe %RAMD%:\waitcd.exe
copy s:\tools\cdgrab.exe %RAMD%:\cdgrab.exe
copy s:\tools\msgbox.exe %RAMD%:\msgbox.exe
rem copy s:\tools\restart.exe %RAMD%:\restart.exe
copy s:\tools\x340.txt %RAMD%:\x340.txt
copy s:\tools\halt.exe %RAMD%:\halt.exe
copy s:\tools\biosupg.txt %RAMD%:\biosupg.txt
rem copy s:\win95\command.com %RAMD%:\command.com
copy a:\command.com %RAMD%:\command.com
copy s:\tools\reboot.com %RAMD%:\reboot.com
copy s:\win95\restart.bat %RAMD%:\restart.bat
REM copy s:\tools\sysinfo.exe %RAMD%:\sysinfo.exe
REM copy s:\tools\syschk.exe %RAMD%:\syschk.exe
copy s:\tools\sticfg.exe %RAMD%:\sticfg.exe
copy s:\tools\sticfg.log %RAMD%:\sticfg.log
copy s:\tools\hwdetect.exe %RAMD%:\hwdetect.exe
copy s:\tools\clini.exe %RAMD%:\clini.exe

REM this is an HP Util named reboot.exe renamed to not conflict with reboot.com
copy s:\tools\reboot4.exe %RAMD%:\reboot4.exe

SET COMSPEC=%RAMD%:\COMMAND.COM

cls

if exist %RAMD%:\win95\mcsboot.exe goto CONTINUE
goto BADHW

:CONTINUE

SET XIMAGE=BADHW

:tools
s:
cd \tools

cls
echo =======================================
echo RUNNING HARDWARE DETECTION . . .
echo =======================================

REM CompaqDetect
REM Systype is a Compaq utility from their SmartStart Scripting Toolkit.
REM Ssstksys.ini contains the BIOS to error level setting for each Compaq Server.
REM Ssstksys.ini was edited to remove all not supported Compaq's.
REM Remember to put errorlevel in descending order.
REM 28 = PL1600 (MCS-7830)
REM 41 = PS720 (MCS-7820/22)
REM 50 = DL380 (MCS-7835-733/1000)
REM 63 = DL320 (MCS-7825-800/1133)
REM 68 = DL380G2 (MCS-7835-1266, MCS-7845-1400)
REM 80 = DL380G3 (MCS-7835H-2.4 / 3.0, MCS-7845H-2.4 /3.0)
REM 83 = DL320G2 (MCS-7825H-2.2 / 3.0)
REM 90 = DL380G4 (MCS-7835-H1, MCS-7845-H1)
REM 255 = Not Compaq Hardware
s:\tools\systype s:\tools\ssstksys.ini
if errorlevel 255 goto IBMDetect
if errorlevel 91 goto IBMDetect
if errorlevel 90 goto DL380G4
if errorlevel 83 set XIMAGE=7825H02
if errorlevel 83 goto 7825H02
if errorlevel 80 goto DL380G3
if errorlevel 68 goto OLDSrv
if errorlevel 63 goto OLDSrv
if errorlevel 50 goto OLDSrv
if errorlevel 42 goto OLDSrv
if errorlevel 41 goto OLDSrv
if errorlevel 28 goto OLDSrv

cls
echo =======================================
echo RUNNING HARDWARE DETECTION . . .
echo =======================================

:IBMDetect
REM Sysinfo.exe was provided by IBM
REM This is used to get the Model number
REM XTYPE = the 7 digit Machine Type / Model
REM XTYPE2 = the 4 digit Macine Type

REM OLD OS 2000.2.4 method
REM %RAMD%:
REM sysinfo >sysinfo.out
REM syschk sysinfo.out
REM Call sysinfo.bat

REM IBM Scripting Toolkit method
%RAMD%:
hwdetect.exe /i >%RAMD%:\hwdetect.txt
clini.exe %RAMD%:\hwdetect.txt /s:System /i:Machine_Type /e:XTYPE2 /b:%RAMD%:\IBMhw1.bat
clini.exe %RAMD%:\hwdetect.txt /s:System /i:Model_Number /e:MODEL /b:%RAMD%:\IBMhw2.bat
clini.exe %RAMD%:\hwdetect.txt /s:System /i:Active_Processors /e:XPROCESSORS /b:%RAMD%:\IBMhw3.bat
clini.exe %RAMD%:\hwdetect.txt /s:System /i:Processor_Speed_MHz.0 /e:CPUSPEED /b:%RAMD%:\IBMhw4.bat

Call IBMhw1.bat
Call IBMhw2.bat
Call IBMhw3.bat
Call IBMhw4.bat
SET XTYPE=%XTYPE2%%MODEL%

if "%XTYPE%"=="847931X" goto OLDSrv
if "%XTYPE%"=="84793AX" goto OLDSrv
if "%XTYPE%"=="867431X" goto OLDSrv
if "%XTYPE%"=="865411Y" goto OLDSrv
if "%XTYPE%"=="865431Y" goto OLDSrv
if "%XTYPE%"=="865441Y" goto OLDSrv
if "%XTYPE%"=="865451Y" goto OLDSrv
if "%XTYPE%"=="86561RY" goto OLDSrv
if "%XTYPE%"=="86566RY" goto OLDSrv
if "%XTYPE%"=="86694RX" goto OLDSrv
if "%XTYPE2%"=="8480" SET XIMAGE=7815I02
if "%XTYPE2%"=="8480" goto 7815I02
if "%XTYPE2%"=="8482" SET XIMAGE=7815I03
if "%XTYPE2%"=="8482" goto 7815I03
if "%XTYPE2%"=="8670" goto IBMX345
if "%XTYPE2%"=="8836" SET XIMAGE=7825I01
if "%XTYPE2%"=="8836" goto 7825I01
if "%XTYPE2%"=="8840" goto IBMX346

goto BADHW

REM ==============================================
REM HP Servers
REM ==============================================

:7825H02
call s:\tools\7825cfg.bat
copy s:\tools\conrep.exe %RAMD%:\conrep.exe /Y
copy s:\tools\HTT_OFF.cfg %RAMD%:\HTT_OFF.cfg /Y
%RAMD%:\conrep /L %RAMD%:\HTT_OFF.cfg
rem copy machine specific system.ini file
copy s:\win95\system.cpq %RAMD%:\win95\system.ini
goto FDISK

:DL380G3
%RAMD%:\sticfg CPU_COUNT
REM Disable HTT
copy s:\tools\conrep.exe %RAMD%:\conrep.exe /Y
copy s:\tools\HTT_OFF.cfg %RAMD%:\HTT_OFF.cfg /Y
%RAMD%:\conrep /L %RAMD%:\HTT_OFF.cfg
IF "%XCPUCNT%"=="2" goto 7845H02
goto 7835H03

:7835H03
Set XIMAGE=7835H03
call s:\tools\783GRcfg.bat
rem copy machine specific system.ini file
copy s:\win95\system.cpq %RAMD%:\win95\system.ini
goto FDISK

:7845H02
Set XIMAGE=7845H02
call s:\tools\7845Rcfg.bat
rem copy machine specific system.ini file
copy s:\win95\system.cpq %RAMD%:\win95\system.ini
goto FDISK

:DL380G4
%RAMD%:\sticfg CPU_COUNT
REM Disable HTT
copy s:\tools\conrep.exe %RAMD%:\conrep.exe /Y
copy s:\tools\HTT_OFF.cfg %RAMD%:\HTT_OFF.cfg /Y
%RAMD%:\conrep /L %RAMD%:\HTT_OFF.cfg
IF "%XCPUCNT%"=="2" goto 7845H03
goto 7835H04

:7835H04
Set XIMAGE=7835H04
call s:\tools\783GRcfg.bat
rem copy machine specific system.ini file
copy s:\win95\system.cpq %RAMD%:\win95\system.ini
goto FDISK

:7845H03
Set XIMAGE=7845H03
call s:\tools\7845Rcfg.bat
rem copy machine specific system.ini file
copy s:\win95\system.cpq %RAMD%:\win95\system.ini
goto FDISK

REM ==============================================
REM IBM Servers
REM ==============================================

:7815I02
s:\tools\stistate.exe
copy s:\win95\system.ibm %RAMD%:\win95\system.ini
goto FDISK

:7815I03
call S:\tools\HTT306.bat
s:\tools\stistate.exe
copy s:\win95\system.ibm %RAMD%:\win95\system.ini
goto PARTINFO

:7825I01
IF "%CPUSPEED%"=="3400" goto BADHW
call S:\tools\HTT306.bat
s:\tools\stistate.exe
copy s:\win95\system.ibm %RAMD%:\win95\system.ini
goto PARTINFO

:IBMX345
REM Disable HTT
a:\IBMNoHT.exe
IF "%XPROCESSORS%"=="2" goto 7845I01

Set XIMAGE=X345
Call s:\tools\IBMRAID7.Bat
s:\tools\stistate.exe
copy s:\win95\system.ibm %RAMD%:\win95\system.ini
goto FDISK

:7845I01
Set XIMAGE=7845I01
Call s:\tools\IBMRAID7.Bat
s:\tools\stistate.exe
copy s:\win95\system.ibm %RAMD%:\win95\system.ini
goto FDISK

:IBMX346
REM Disable HTT
a:\X346NoHT.exe
IF "%XPROCESSORS%"=="2" goto 7845I02

Set XIMAGE=7835I02
Call s:\tools\IBMRAID.Bat
s:\tools\stistate.exe
copy s:\win95\system.ibm %RAMD%:\win95\system.ini
goto FDISK

:7845I02
Set XIMAGE=7845I02
Call s:\tools\IBMRAID.Bat
s:\tools\stistate.exe
copy s:\win95\system.ibm %RAMD%:\win95\system.ini
goto FDISK

REM ==============================================
REM Get Partition information
REM ==============================================

:FDISK
REM Used to determine the state of the hard drive based on the partitions.
s:\tools\fdisk.exe /info /tech > %RAMD%:\part.txt
s:\tools\fdskpart.exe
cls
goto COMMON

:PARTINFO
REM IBM X330, X206, and X306 do not work correctly with fdisk still using partinfo
REM They run extrememly slow and do not load the Win95 shell or run Drive Image Pro.
REM Used to determine the state of the hard drive based on the partitions.
s:\tools\partinfo.exe > %RAMD%:\part.txt
s:\tools\stipart.exe
cls
goto COMMON

:COMMON
a:\smartdrv.exe %RAMD%+ s 1024 1024

MsgBox "PLEASE WAIT AS THE CISCO SERVER" "AUTOMATED SETUP CONTINUES TO LOAD"
%RAMD%:

goto end

REM ==============================================
REM Error Messages
REM ==============================================

:HALT

%RAMD%:\cdgrab e s > nul
%RAMD%:\stinocad
%RAMD%:\MsgBox /T:%RAMD%:\Hwout.txt /w /B:BLUE /F:WHITE
%RAMD%:\halt.exe

:OLDSrv

cls
copy a:\OLDSrv.bat %RAMD%:\OLDSrv.bat
cls
set comspec=%RAMD%:\command.com
cls

call %RAMD%:\OldSrv.bat

:BADHW

cls
copy a:\end.bat %RAMD%:\end.bat
cls
set comspec=%RAMD%:\command.com
cls

call %RAMD%:\end.bat

:end

I try "set XIMAGE=x345 goto IBMx345","SET XIMAGE=7815 goto IBM7815" and "set XIMAGE=7830 goto CPQ7830",and all three methods
do not work.

Would you pls tell me how to change the above autoexec.bat file?

very thanks your help!!

Hi Jason and all

when you do the fdimage you obtain a floppy. How are you able to read the floppy ?

My issue is that after doing the fdimage, my floppy becomes unreadable and of course I cannot go ahead with the next steps.

Thanks for the help

Xav

Hi all

Was anyone successful in installing CCME 5 on non Cisco hardware?

Thanks
Bruno

Yeah CM 5 supports vmware natively.

not sure about non-cisco hardware though.

I'm trying to install 4.1(3) under VMWare, ... I was able to get around the RAID error by commenting out the "Call s:\tools\IBMRAID7.Bat" line.

I had to manually partition the VMWare partition - used fdisk.exe which the CCM install has conveniently located in the CDROM's tools\ directory.

Problem now ~ I can get to where the GUI comes up and asks if you want to continue ... Then a small blue window pops up saying "preparing base image" and the install hangs.

Wondering if maybe I need to format the VMWare partition before attempting the install??? Will try that next.

It's painfully slow waiting for the GUI to come up ... the "Cisco Systems Empowering the Internet Generation" graphic stays up for about 20 minutes.

Thanks in advance,

Joe

Hello,
Did anybody find the solution from the previous question? (Cannot find System.ini.
You need to run Windows Setup again to install the file) I have the same problem..
Thanks...

Hi All,

Well I have been getting the opposite with regards to VMware. First off, I have configured the image as IDE, so at this time I don’t need to worry about SCSI drivers and a-like.

When I get into the MCSboot with no partitions configured I get the blue windows, where it hangs and stops responding, but when I have configured partitions and formatted them it hangs as it boots win95 and doesn’t even get to the MCSboot.

What would really help is if someone could acquire the drive.ini file from a working install of a flat build or even a complete build. I am thinking this is the main crocks of the problem as this is the file used to tell MCSboot how to configure the partitions or even how they are configured. But I might be pissing into the wind here!

If anyone could do this for me and needs help, please let me know. It only needs someone to put command.com at the end of the autoexec.bat file and copy the drive.ini from the Ram disc.

Many thanks,

Hi all,

i am able to install callmanager v3.3.4 on non-MCS equipment. I am able to route and place calls. The problem I face is with IP Phone services. When I try to connect to a service, the ip phone always display "Host not Found!".

Can anyone please help?

HERE IT IS >>> The WORKING VMWARE INSTALLATION INSTRUCTIONS!!! WOOHOO!!!

Step 1: Download a Windows utility called FDIMAGE.EXE. This is typically used to create floppy boot disks from disk images for BSD/Linux. I've attached it ... Rename the file to fdimage.exe

Step 2: Pop in in the CallManager Hardware Detect CD-ROM (Disk 1) into your PC

Step 3: Put in a blank floppy disk

Step 4: Open a command prompt and type "fdimage d:\bootimg.bin a:" this copies the boot image from the CD-ROM to the floppy disk

Step 5: On the floppy disk, edit the autoexec.bat file (I'm having flashbacks to the MS-DOS days)

Step 6: Find the line in the autoexec.bat file that says "s:\tools\systype s:\tools\sssksys.ini" This line is right before the boot process does the hardware check to see what sort of server you have

Step 7: Hit enter after the above line and add the following two lines:
set XIMAGE=x345
goto IBMx345

Step 8: Add a REM statement to the IBMRAID7.Bat line under the Set Ximage=X345

Set XIMAGE=X345
REM Call s:\tools\IBMRAID7.Bat

Step 9: Save the file

Step 10: Using the CD Burning software of your choice (I used Nero version 6), use the extracted contents of the BOOTIMG.BIN (on the floppy you just created) to create a new bootable Hardware Detect CD.

Step 10a: Copy the contents of the Hardware Detect CD to a folder on your hard drive. DO NOT COPY THE BOOTIMG.BIN FILE!!! We're going to use the modified files extracted from the original BOOTIMG.BIN in step 4, and burn those back onto the new CD-ROM. Here's what the directory should look like ...

Arco (directory)
Erase (directory)
Extract (directory)
Images (directory)
Raidbio7 (directory)
Raidbios (directory)
Tools (directory)
Win95 (directory)
2000_2_7 (filename)
Bootcat.bin (filename)

Remove CD.

Step 10b: Insert blank CD-ROM. Make sure that the boot floppy created in Step 4 (with the new autoexec.bat) is in the floppy drive.

Step 10c: Start Nero, and under "New Compilation" select CD-ROM (Boot). Under the "Boot" Tab, "Source of boot image data" make sure to select "Bootable logical drive (must fit on the CD!)" Under the drop down, make sure that your floppy drive is selected "A:\1.44MB"

Step 10d: On the left side of the screen, click "New"

Step 10e: Nero will now bring up a split screen, with the right side showing the contents of your computer, and the left side showing the contents of the CDROM. Double click on the folder you created in step 10a. Drag the contents of the folder (not the folder itself!) over to the CD-ROM

Don't worry - You won't see the BOOTIMG files here as this point. You should see all of the folders, and two files listed in Step 10a Under the "ISO1" on the left side of the screen.

Step 10f: Select Recorder, Burn this Compilation. Under "Action" make sure that "Write" and "Finalize CD" are selected. Click on Burn.

As long as your floppy disk created in Step 4, with the new autoexec.bat from Step 5 is in the floppy drive, Nero will begin copying the boot files from the floppy back onto the new blank CD. Once that part is complete, Nero will then copy the contents of the original CD off of your hard disk from the folder created in Step 10a.

Once this is complete you will no longer need the boot floppy. This will DRAMATICALLY speed up the installation process, vice using the floppy.

Step 11: Create a new Virtual Machine in VMWare.

Step 11a: For Virtual Machine Configuration, select "Custom". For Guest Operating System select "Microsoft Windows" and version select (believe me on this one) Windows 95.

The install shell that Cisco uses for the Hardware detect CD runs on a stripped down version of Win 95, and if you select Win2K, the install will hang.

Select next, and provide whatever VM Name and location you desire.

Select next, and uncheck "Make this VM Private" ... unless you want it private.

Select next, and Run this VM as user that powers on the virtual machine. The assumption is that you will power it up with Admin Rights, and this requires no change.

Select next and number of processors = 1

Select next and set "Memory for this VM" as 1024 MB. Very Important for CCM 4.1(3)

Select next and select "Use Bridged Networking" (default)

Select next and leave I/O Adapter Types set to ATAPI and BusLogic

Select next and "Create New Virtual Disk"

Select Next and "Virtual Disk Type" is IDE (NOT SCSI)

Select Next and Disk Capacity - Assign a MINIMUM of 8GB. Select Allocate Disk Space now for optimal performance.

Select Next - Disk File - Enter in a descriptive name for the VM files. CCMPUB.vmdk or whatever ... It will default to Windows 95.vmdk, so I suggest changing it.

Select Finish

Step 12: Insert the newly created bootable CD-ROM from Step 10f. Start the VM. Follow the wizard to blow the Windows 2000 image onto the non-MCS machine. It will prompt you for the OS Disk 3 (I'm using DVDs - it's DVD #3 of the OS install for me). You will need a DVD Drive for this ... Once the install detects the DVD, you'll get the "Power Quest Drive Image Pro" application, and the OS will be imaged on to the VM.

DANGER WILL ROBINSON!!!

After the windows install appears to be complete, you will be given a "Found New Hardware" box. DO NOT CLICK INSTALL NOW!!! CLICK CANCEL. DO NOT CLICK "Reboot Now" when prompted by the "Windows has finished installing new devices" dialog box.

WAIT WAIT WAIT until the OS Install completes the "Writing System Configuration" and it will reboot the VM all by itself.

Step 13: After Windows comes online, login and install VM tools. This will install the appropriate video and NIC drivers.

Step 14: Pop in the Cisco CallManager CDs and proceed as normal! This rocks!

Of course, this is only in a lab environment. The great Cisco powers that be would definitely frown upon a TAC support call from a Cisco 4.1(3) CallManager running on a VM Instance.

Start to finish, once you have the new Hardware Detect CD from Step 10, The VM Install took me about 2 1/2 hours ... the longest part being the actual CallManager CD1 & CD2 install.

You just beat me to the punch!!!

I would say the main solution to the long pause on the "Cisco Systems Empowering the Internet Generation" screen and when the blue window that states "preparing base image…" stops responding, is to telling VMware to use Windows 95 as its ‘Guest operating system’.

Also it would be advised to change the VMware images ‘Guest operating system’ settings back to ‘Windows 2000 Advanced Server’ when it complete the image restore. This can be found under the options of the VMware image.

Hi Mark
Thanks for the detailed explanation above
I wonder if you can help

I got to the stage 12 too insert OS disk 3,I inserted the second disk which is a DVD and it wont have it just says wrong media and ejects it.

I am installing version 4.1(3) on a HP DL360G3 and the disks I have are OS CD1 2000 2.7 and OS DVD2 2000 2.7

Please any ideas on how I can get this installed?

Cheers

Chays

Hi Chays,

My instructions above are for a VM install. Are you trying to install under a VM, or just a native install on the DL360? You will need the modified Hardware Detect CD-ROM as well. Do you have that? The whole premise of getting this to work is installing the generic IBM X345 image, which uses IDE drivers, which is resident on OS DVD Disk 3 ... DVD 2 won't work.

If you are trying to do a native install on the box, the same applies, though you will also need to make sure you have IDE drives in your DL360, otherwise you'll get the BSOD when Win2K tries to boot.

Hope this helps ... let me know if you have any other Q's

joe

Hi Joe
Thanks for your reply
After making the hardware detect CD from the instructions above I created the new Virtual machine image and tried and then tried the install it stared all well till it asked for the OS DVD Disk 3.
As I said above I have only two disks
1. OS CD1 2000 2.7
2. OS DVD2 2000 2.7

Is there a way I can modify anything for it to continue the install from DVD Disk2 rather than DVD Disk3?

Surprisingly I also tried this install on the actual box and it went through!up to the point of asking for the DVD Disk3!

Any ideas?

Hi Joe
Dont know if its worth mentioning that the two disks above have been used to successfully install the OS on a DL380 G3 box
Look forward to any help from you

Cheers

Wondered if you could help. I am trying to install Call Mananager 4.1(2)on a non-MCS machine. I have made the following registry hacks:
[HKEY_LOCAL_MACHINE\SOFTWARE\Cisco Systems\Model]
"Hardware"="MCS7835"
"Memory"="512"
"Speed"="1000"
"@"=""
[HKEY_LOCAL_MACHINE\SOFTWARE\Cisco Systems\Spirian]

[HKEY_LOCAL_MACHINE\SOFTWARE\Spirian\System Info\OS Image]
"Version"="2000.2.7"

I then installed the 2000.2.7 upgrade and then ran the setup program. Everything looked okay until half way through the second disk, it suddenly bombed out and failed. When I looked at the log file I saw the following output:

Action 11:27:24: MSICheckForDCDFailure.
11:27:26: MSIApi.cpp: MSICheckForDCDFailure: Function Started
11:27:26: MSIApi.cpp: MSICheckForDCDFailure: Opened registry key
11:27:26: MSIApi.cpp: MSICheckForDCDFailure: Retrieved status of DCD install
11:27:26: MSIApi.cpp: MSICheckForDCDFailure: 0
11:27:26: MSIApi.cpp: MSICheckForDCDFailure: Cisco Directory install succeed
11:27:26: MSIApi.cpp: MSICheckForDCDFailure: Function Ended
Action 11:27:26: InstallODBC. Installing ODBC components
Action 11:27:26: StartServices. Starting services
Action 11:27:26: MSICreateProcessWithLogon_CCM_PubFresh. Installing Cisco CallManager
12/11/2006 11:27:27.496(W) --> MSICreateProcessWithLogon()
12/11/2006 11:27:27.506(W) GetComputerName computername: WARBNET-9714624
12/11/2006 11:27:27.506(W) Initializing data buffer
12/11/2006 11:27:27.506(W) Retrieving "CustomActionData" property
12/11/2006 11:27:27.506(W) Parsing string into tokens
12/11/2006 11:27:27.506(W) Password:
12/11/2006 11:27:27.516(W) Program : "C:\CCMTmp\CCM\Setup.exe"
12/11/2006 11:27:27.516(W) Params : -s -f1"C:\CCMTmp\CCM\CCM_Pub.iss" -f2"C:\Program Files\Common Files\Cisco\Logs\CCM.log" -SMS
12/11/2006 11:27:27.516(W) Connecting to SCM
12/11/2006 11:27:27.516(W) Return code: [0]
12/11/2006 11:27:27.516(W) Enabling "seclogon" service
12/11/2006 11:27:28.587(W) Return code: [0]
12/11/2006 11:27:28.587(W) Starting "seclogon" service
12/11/2006 11:27:28.597(W) Return code: [0]
12/11/2006 11:27:43.599(W) Setting startup parameters for EXE
12/11/2006 11:27:43.599(W) Creating command-line string for launching EXE
12/11/2006 11:27:43.599(W) "C:\CCMTmp\CCM\Setup.exe" -s -f1"C:\CCMTmp\CCM\CCM_Pub.iss" -f2"C:\Program Files\Common Files\Cisco\Logs\CCM.log" -SMS
12/11/2006 11:27:43.599(W) Calling CreateProcessWithLogonW()
12/11/2006 11:27:43.709(W) Successfully launched EXE
12/11/2006 11:27:43.709(W) Waiting for process to exit
12/11/2006 11:28:48.933(W) Return code: 0
12/11/2006 11:28:49.043(W) Stopping "seclogon" service
12/11/2006 11:28:51.076(W) Return Code: [0]
12/11/2006 11:28:51.076(W) Disabling "seclogon" service
12/11/2006 11:28:52.218(W) Return Code: [0]
12/11/2006 11:28:52.218(W) Action 11:28:52: MSICheckForCCMFailure.
11:28:54: MSIApi.cpp: MSICheckForCCMFailure: Function Started
11:28:54: MSIApi.cpp: MSICheckForCCMFailure: Opened registry key
11:28:54: MSIApi.cpp: MSICheckForCCMFailure: Retrieved status of CallManager install
11:28:54: MSIApi.cpp: MSICheckForCCMFailure: 1
11:28:54: MSIApi.cpp: MSICheckForCCMFailure: CallManager install failed.
11:28:54: MSIApi.cpp: MSICheckForCCMFailure: Message displayed: Failure occured during the Cisco CallManager installation.
Please look at the Cisco CallManager installation log files for details.
Aborting Cisco CallManager install.
11:30:32: MSIApi.cpp: MSICheckForCCMFailure: Function Ended
Action ended 11:30:32: InstallFinalize. Return value 3.
Action 11:30:32: Rollback. Rolling back action:
Action ended 11:30:33: INSTALL. Return value 3.

I'm not sure however what this relates to. Any help would be appreciared

Thanks

Ian

i'm using OS version 2000.4.3(a) hardware detection cd, after run "fdimage d:\image1.bin a:", I can't even access the floppy disk let alone editing the autoexec.bat file and this is the error message I got when it tried;

C:\>dir a:
The volume does not contain a recognized file system.
Please make sure that all required file system drivers are loaded and that the v
olume is not corrupted.

I'm try to install ccm 4.2.3 on a IBM PC. It is only for my home lab to practise CCM. Anybody got any ideas how to overcome this problem??

Hi all,
Has anyone tried the "WORKING VMWARE INSTALLATION INSTRUCTIONS" using CCM4.2(1) media?
I get to step 12, boot into the DVD and it runs through the hardware detect / WinPE then complains saying the media I'm using isn't compatible with the hardware I have....

any ideas?

thanks.

Hello everyone. Thanks to everyone for contributing their experiences with trying to get Callman running on non-MCS hardware.

After much trial and error I finally got the OS running on a Dell Precision 350 using the XIMAGE=X345 parameter and v3.3(3) install disk 3.

However, when I attempt to install Callman 3.3(3) on the box I get through the steps of setting up the various passwords, but when I select the "Install" button I immediately get the following error: "Failure occured trying to get DBNAME value from registry. Aborting Cisco CallManager installation." This is recorded as Event ID 1013, source MsiInstaller.

I haven't had much luck locating any information on what this error means and what to do about it other than "reinstall CallManager", which is what I'm am trying to do.

Any suggestions from anyone would be appreciated. Thanks!

Hi, I installed publisher with CM4.2 (using CD) and then patched up to 4.2.3. I then used the same CD (4.2) to install a subscriber but it's not allowing me to beacuse it says that publisher database has a different verison. Do you know any workaround with this without uninstalling the publisher?

Hope you could help me with this. Thanks.
JB

Whoever posted that point about making the guest OS on VMWare Windows 95...................

THANK YOU VERY VERY MUCH INDEED!!!!!!!

Works a treat. For those who are interested, I am using 2000.2.3 OS discs and floppy tricked it using IBM7815.

Thanks again

Martin

Hi all,
When I tried the "WORKING VMWARE INSTALLATION INSTRUCTIONS" using for CCM4.2(1) media, I had inserted "Cisco IP TELEPHONY SERVER OS 2000.4.3(a)" and typed "fdimage e:\bootimg.bin d:" = And I saw the next message:

C:\>fdimage e:\bootimg.bin b:
e:\bootimg.bin - No such file or directory

What is the correct name hw detection file?

Can anybody help me with CCM4.2?

I have been unable to load 2000.2.7 on VPC.
Tryed most versions (X345, 7815H02, ...)
and all hang after installing, on first boot.
(After loading windows "piano" display)

Anyone able to load this on VPC can chime in ?

I have gotten about as far as Ian (Chays) has. Everything works great until it bombs out installing the Cisco Directory.

the CCMDBSetup log finishes with this...

AddNTUser: ccm CCMUser **********
Failed to create CCMUser Windows Webusers Account.

I went and checked on the group membership of that user, it was blank. I added them to users and will install again here in a few mins. Ill post again the results.

This is on a Win 2000 Server box. I am installing CCM 4.13 with update 2000-4-2sr4.

I'll post again here shortly.

Thanks for the postings I was able to load CCM on a Dell PC. I had trouble with FDIMAGE.EXE but switched Rawwrite. I edited the Autoexec file and changed the set XIMAGE=x345
goto IBMx345 to Set XIMAGE=7845H02 and it worked great. I now have Publisher and Subscriber running in my lab. Thanks to all who contributed to the posts.

Ok if I want to install OS with different MCS hardware version can I use the same procedure.

I have the same issue as Martin. I have OS 2000.4.4 and there isn't a bootimg.bin on the CD.

My Contents that I have are:

11/15/2006 07:18 PM HP
11/15/2006 07:18 PM I386
11/15/2006 07:23 PM IMAGES
11/15/2006 07:18 PM POSTINSTALL
07/27/2004 11:41 AM 150 WINNT.SIF
11/15/2006 07:26 PM 187,301,888 WINPE.ISO

Any ideas anyone?

The newer installation DVDs don't have a hardware detection CD at all, so the method discussed here won't work. I believe this change corresponded with the introduction of the SATA based 7825 hardware. I believe that the OS Install DVD is created with "sysprep", but I am not a Windows admin so I don't know much about it.

If you have a CD set with a Hardware Detection CD, you can attempt this method. I tried with 2.7 on a new Dell desktop with SATA HD and DVD and it was a bust. Found a driver for the SATA DVD, but it cannot start Windows 95. Probably doomed to failure because I doubt if any of the images have SATA disk drivers.

We did get one working by loading Win2k SP4 manually and using registry hacks, but it was a nightmare. You may have to manually create the "WebUsers" group when the CallManager setup blows off. Also don't forget D: volume "STI_DATA".

The new OS installation DVD, as it was told here, have no bootimg.bin file, and whole installation process is different. When I first designed and published the floppy trick, Cisco was using Windows 95 to deploy OS images (that's why on VMWare you have to select Windows 95 machine type). At certain stage they tried to overcome the floppy trick by increasing the size of bootimg.bin for just a couple bytes, so it won't fit into the floppy, but people were creating a Windows 95 bootable floppy, and then just copy all files to the floppy.

Now they use WinPE Preconfigured Environment (this is what the WinPE.ISO file is). I was successful once to modify the installation to run on non-MCS platform, but these modifications are not that straight, require additional software and re-burning DVD. The basic idea is:

1. Create an ISO file from the installation DVD and store it on your PC. Open the ISO file, and copy WINPE.ISO file to your PC, find and and extract the OSINST.VBE file (this is actual installation script). You will need a software to manipulate an ISO images (ISOBuster, UnDisker, etc.)

2. Since the OSINST.VBE is encrypted, you need to decrypt it. I found the VB script ScriptDEcoder.vbs, which does the thing. As a result you will have the OSINST.VBS script in readable format.

3. Learn how script detects the platform, and disable detections (I did a couple modifications and defined the platform as 7825H02).

4. Rename the modified OSINST.VBS to OSINST.VBE, copy it back into the WINPE.ISO file, and then copy the modified WINPE.ISO back to the Installation DVD.

5. Burn DVD and try to boot with it.

Theoretically you may copy the resulting ISO image into the USB drive (HP has the utility to do this). In this case if something does not work, you don't have to re-burn a new DVD.

As I told, I was successful once, but it was a lot of work and a lot of variables to accomplish this. So, it's possible, bot does it worth it?

Good luck,

Mike S

------

Headset Adapters for Cisco IP Phones
www.ciscoheadsetadapter.com

The new OS installation DVD, as it was told here, have no bootimg.bin file, and whole installation process is different. When I first designed and published the floppy trick, Cisco was using Windows 95 to deploy OS images (that's why on VMWare you have to select Windows 95 machine type). At certain stage they tried to overcome the floppy trick by increasing the size of bootimg.bin for just a couple bytes, so it will not fit into the floppy, but people were creating a Windows 95 bootable floppy, and then just copy all files to the floppy.

Now they use WinPE Preconfigured Environment (this is what the WinPE.ISO file is). I was successful once to modify the installation to run on non-MCS platform, but these modifications are not that straight, require additional software and re-burning DVD.

The new OS installation DVD, as it was told here, have no bootimg.bin file, and whole installation process is different. When I first designed and published the floppy trick, Cisco was using Windows 95 to deploy OS images (that's why on VMWare you have to select Windows 95 machine type). At certain stage they tried to overcome the floppy trick by increasing the size of bootimg.bin for just a couple bytes, so it will not fit into the floppy, but people were creating a Windows 95 bootable floppy, and then just copy all files to the floppy.

The new OS installation DVD, as it was told here, have no bootimg.bin file, and whole installation process is different. When I first designed and published the floppy trick, Cisco was using Windows 95 to deploy OS images (that is why on VMWare you have to select Windows 95 machine type). At certain stage they tried to overcome the floppy trick by increasing the size of bootimg.bin for just a couple bytes, so it will not fit into the floppy, but people were creating a Windows 95 bootable floppy, and then just copy all files to the floppy.

The new OS installation DVD, as it was told here, have no bootimg.bin file, and whole installation process is different. When I first designed and published the floppy trick, Cisco was using Windows 95 to deploy OS images (that is why on VMWare you have to select Windows 95 machine type). At certain stage they tried to overcome the floppy trick by increasing the size of bootimg.bin for just a couple bytes, so it will not fit into the floppy, but people were creating a Windows 95 bootable floppy, and then just copy all files to the floppy.

Mike S

Headset Adapters for Cisco IP Phones

www.ciscoheadsetadapter.com

The new OS installation DVD, as it was told here, have no bootimg.bin file, and whole installation process is different. When I first designed and published the floppy trick, Cisco was using Windows 95 to deploy OS images (that is why on VMWare you have to select Windows 95 machine type). At certain stage they tried to overcome the floppy trick by increasing the size of bootimg.bin for just a couple bytes, so it will not fit into the floppy, but people were creating a Windows 95 bootable floppy, and then just copy all files to the floppy.

Mike S

Headset Adapters for Cisco IP Phones

www.ciscoheadsetadapter.com

The new OS installation DVD, as it was told here, have no bootimg.bin file, and whole installation process is different. When I first designed and published the floppy trick, Cisco was using Windows 95 to

deploy OS images (that is why on VMWare you have to select Windows 95 machine type). At certain stage they tried to overcome the floppy trick by increasing the size of bootimg.bin for just a couple bytes, so

it will not fit into the floppy, but people were creating a Windows 95 bootable floppy, and then just copy all files to the floppy.

Now they use WinPE Preconfigured Environment (this is what the WinPE.ISO file is). I was successful once to modify the installation to run on non-MCS platform, but these modifications are not that

straight, require additional software and re-burning DVD. The basic idea is:

1. Create an ISO file from the installation DVD and store it on your PC. Open the ISO file, and copy WINPE.ISO file to your PC, find and and extract the OSINST.VBE file (this is actual installation

script). You will need a software to manipulate an ISO images (ISOBuster, UnDisker, etc.)

2. Since the OSINST.VBE is encrypted, you need to decrypt it. I found the VB script ScriptDEcoder.vbs, which does the thing. As a result you will have the OSINST.VBS script in readable format.

3. Learn how script detects the platform, and disable detections (I did a couple modifications and defined the platform as 7825H02).

4. Rename the modified OSINST.VBS to OSINST.VBE, copy it back into the WINPE.ISO file, and then copy the modified WINPE.ISO back to the Installation DVD.

5. Burn DVD and try to boot with it.

Theoretically you may copy the resulting ISO image into the USB drive (HP has the utility to do this). In this case if something does not work, you do not have to re-burn a new DVD.

As I told, I was successful once, but it was a lot of work and a lot of variables to accomplish this. So, it is possible, bot does it worth it?

Good luck,

Mike S

Headset Adapters for Cisco IP Phones

http://www.ciscoheadsetadapter.com

The new OS installation DVD, as it was told here, have no bootimg.bin file, and whole installation process is different. When I first designed and published the "floppy trick" on VoiceIE.com, Cisco was using Windows 95 to deploy OS images (this why on VMWare you have to select Windows 95 machine type). At certain stage they tried to overcome the floppy trick by increasing the size of bootimg.bin for just a couple bytes, so it will not fit into the floppy, but people were creating a Windows 95 bootable floppy, and then just copy all files to the floppy.

Now they use WinPE Preconfigured Environment (this is what the WinPE.ISO file is). I was successful once to modify the installation to run on non-MCS platform, but these modifications are not that straight, require additional software and re-burning DVD. The basic idea is:

1. Create an ISO file from the installation DVD and store it on your PC. Open the ISO file, and copy WINPE.ISO file to your PC, find and and extract the OSINST.VBE file (this is actual installation

script). You will need a software to manipulate an ISO images (ISOBuster, UnDisker, etc.)

2. Since the OSINST.VBE is encrypted, you need to decrypt it. I found the VB script ScriptDEcoder.vbs, which does the thing. As a result you will have the OSINST.VBS script in readable format.

3. Learn how script detects the platform, and disable detections (I did a couple modifications and defined the platform as 7825H02).

4. Rename the modified OSINST.VBS to OSINST.VBE, copy it back into the WINPE.ISO file, and then copy the modified WINPE.ISO back to the Installation DVD.

5. Burn DVD and try to boot with it.

Theoretically you may copy the resulting ISO image into the USB drive (HP has the utility to do this). In this case if something does not work, you do not have to re-burn a new DVD.

As I told, I was successful once, but it was a lot of work and a lot of variables to accomplish this. So, it is possible, bot does it worth it?

Good luck,

Mike S

Headset Adapters for Cisco IP Phones

www.ciscoheadsetadapter.com

The new OS installation DVD, as it was told here, have no bootimg.bin file, and whole installation process is different. When I first designed and published the "floppy trick" on VoiceIE.com, Cisco was using Windows 95 to deploy OS images (this why on VMWare you have to select Windows 95 machine type). At certain stage they tried to overcome the floppy trick by increasing the size of bootimg.bin for just a couple bytes, so it will not fit into the floppy, but people were creating a Windows 95 bootable floppy, and then just copy all files to the floppy.

Now they use WinPE Preconfigured Environment (this is what the WinPE.ISO file is). I was successful once to modify the installation to run on non-MCS platform, but these modifications are not that straight, require additional software and re-burning DVD. The basic idea is:

1. Create an ISO file from the installation DVD and store it on your PC. Open the ISO file, and copy WINPE.ISO file to your PC, find and and extract the OSINST.VBE file (this is actual installation

script). You will need a software to manipulate an ISO images (ISOBuster, UnDisker, etc.)

2. Since the OSINST.VBE is encrypted, you need to decrypt it. I found the VB script ScriptDEcoder.vbs, which does the thing. As a result you will have the OSINST.VBS script in readable format.

3. Learn how script detects the platform, and disable detections (I did a couple modifications and defined the platform as 7825H02).

4. Rename the modified OSINST.VBS to OSINST.VBE, copy it back into the WINPE.ISO file, and then copy the modified WINPE.ISO back to the Installation DVD.

5. Burn DVD and try to boot with it.

Theoretically you may copy the resulting ISO image into the USB drive (HP has the utility to do this). In this case if something does not work, you do not have to re-burn a new DVD.

As I told, I was successful once, but it was a lot of work and a lot of variables to accomplish this. So, it is possible, bot does it worth it?

Good luck,

Mike S

Headset Adapters for Cisco IP Phones

www.ciscoheadsetadapter.com

The new OS installation DVD, as it was told here, have no bootimg.bin file, and whole installation process is different. When I first designed and published the "floppy trick" on VoiceIE.com, Cisco was using Windows 95 to deploy OS images (this why on VMWare you have to select Windows 95 machine type). At certain stage they tried to overcome the floppy trick by increasing the size of bootimg.bin for just a couple bytes, so it will not fit into the floppy, but people were creating a Windows 95 bootable floppy, and then just copy all files to the floppy.

Good luck,

Mike S

Headset Adapters for Cisco IP Phones

www.ciscoheadsetadapter.com

The new OS installation DVD, as it was told here, have no bootimg.bin file, and whole installation process is different. When I first designed and published the "floppy trick" on VoiceIE.com, Cisco was using Windows 95 to deploy OS images (this why on VMWare you have to select Windows 95 machine type). At certain stage they tried to overcome the floppy trick by increasing the size of bootimg.bin for just a couple bytes, so it will not fit into the floppy, but people were creating a Windows 95 bootable floppy, and then just copy all files to the floppy.

Now they use WinPE Preconfigured Environment (this is what the WinPE.ISO file is). I was successful once to modify the installation to run on non-MCS platform, but these modifications are not that straight, require additional software and re-burning DVD. The basic idea is:

1. Create an ISO file from the installation DVD and store it on your PC. Open the ISO file, and copy WINPE.ISO file to your PC, find and and extract the OSINST.VBE file (this is actual installation script). You will need a software to manipulate an ISO images (ISOBuster, UnDisker, etc.)

2. Since the OSINST.VBE is encrypted, you need to decrypt it. I found the VB script ScriptDEcoder.vbs, which does the thing. As a result you will have the OSINST.VBS script in readable format.

3. Learn how script detects the platform, and disable detections (I did a couple modifications and defined the platform as 7825H02).

4. Rename the modified OSINST.VBS to OSINST.VBE, copy it back into the WINPE.ISO file, and then copy the modified WINPE.ISO back to the Installation DVD.

5. Burn DVD and try to boot with it.

Theoretically you may copy the resulting ISO image into the USB drive (HP has the utility to do this). In this case if something does not work, you do not have to re-burn a new DVD.

As I told, I was successful once, but it was a lot of work and a lot of variables to accomplish this. So, it is possible, bot does it worth it?

Good luck,

Mike S

Headset Adapters for Cisco IP Phones

www.ciscoheadsetadapter.com

Hi,

I have tried to create the floppy disk as described but when I view the files there are 3 missing autoexec.bat command.com and config.sys. Does anybody have any ideas on how to achieve all the files on the disk.

Many thanks

Sean

I'm trying this setup but in my autoexec.bat file this line is missing s:\tools\systype s:\tools\sssksys.ini can some one please assist me with this cause I can go any further with the reroot.

Thanks

The installation started fine untill it requested the OS2.
After inserting OS2 DVD the system does not detect the DVD as the right one??????????

Thanks for the help.

I have been looking for CLINI.exe for years, can anyone help me find it? Id do anything at this point.

Wow.. This sure has come a long way since the original media was hacked!!

I'm now trying to install Unity 5.01 (with os 2003.1.2) on a "slightly older than allowed" 7825 box, so I'm back to this site to find out what's new..

And, I find "ScriptDEcoder.vbs"... I've been fighting with it for 30 minutes, and it's not doing ANYTHING, 'till I realized that the .VBE file came out of the ISO image with UPPER CASE VBE... The decode script looks specifically for lower case vbe, so... if the script decode isn't working for you, just rename the vbe to make it lower case!

Good luck, and see ya next time!
-Steve

I am installing CallManager 4.2.3 on VPC (win2k server) CallManager CD1 installed successfully, but couldn’t install CD2 successfully and I got the following statement in the log file ” Failed to create CCMuser windows webusers account” .. any idea how to solve this problem?

Thanks
Ray

I am having a problem getting Call Manager 4.1.4 with sr7, to recognize an ip communicator. Anyone know if there are specific instructions on adding one of these phones? I am able to get the date/time information when booting software and it gets the config but it never pulls a dn.

Any thoughts our suggestions would be great.

Thanks

Bryan

i created the floppy disk and installed w2k with disk 3. updated nic driver and tried installing CCM and received an error "Current OS version does not meet the minimum requirement. im installing on a DELL Optiplex GX620

Hi guys need your help am trin 2install the call manager6 on a vmware i have managed to tweak the registry i am installing it on a Cisco MCS 7800 i have added enough RAM and Harddisk space to the installation starts but somewhere in the middle it stops giving me this error dumping diagnostic files please insert USB Drive i do that still it gives me the same error. i also want to run a vmware of the cisco IP Telephony software but once it starts it gives me this Error: Drive Size Fatal Error yet i have also allocated around 40gb of space to it and yet it says its not the 8 gigabytes that are needed can someone please help thanks

I have fixed this by allocating 148.0 GB for the drive when I create the VM, for weeks I had these disk issues and just changing that number even though we are not allocating that much took care of the issue me.

Dave