[sims] Manually installing on Win 7 pro 64 bit - unsupported 16 bit application

[Koldov]

Hi All,

 

Does anybody know a workaround for this? I cannot install SIMS on this laptop due to the error below?

 

 

Using SOLUS 2.

 

Running SIMSINST.

 

Kol

[vikpaw]

Is it your first 64bit install? Is your setups folder up to date? I don't have that file on my system.

Sounds like a file you'd find on an old setup diskette. Is it SIMS you're trying to install, or nova or something else.

[Koldov]

Yeah just SIMS - first time 64 bit, I have been avoiding going to it just for this type of reason (given compatibility with educational software), the setups folder is ancient. SIMSINST is from 2005... But each SOLUS update I have check for newer program files ticked... But it has never changed. Edited December 1, 2014 by Koldov

[matt40k]

SOLUS2 doesn't update SIMSINST.

[Koldov]

Where would I get a new version then?

 

Although there are newer files in the setups folder, I can't upload a screenshot now - Should I use one of those?

 

SIMSManualSetup

SIMSApplicationSetup

SIMSSQLApplicationSetup

 

These are from 2014...

[matt40k]

Contact Capita\LA. If they're kind they'll give you a zip with just the files SOLUS2 doesn't update, if they're not, you'll get sent a ISO and you'll have to extract and copy over the files. Cheats way would be to run simsapplicationsetup.exe, that'll get SIMS installed and when you run SIMS, SIMSload will install the remainder (ie sims manual setup etc). For the win, setup SOLUS3.

[Koldov]

Contact Capita\LA.

 

Was trying to avoid that!

 

Cheats way

 

That's why I'm here!

 

For the win, setup SOLUS3.

 

Is that really a win nowadays? Saw it in a Nursery School I used to support a couple of years ago and what an ugly, unresponsive, hard to navigate beast that was.... I had to look at why it wasn't updating the workstations, so went onto the server and fired it up - couldn't even work out what was what (not very intuitive) and was just faced with a 3 page list of failed, not downloaded, half downloaded or not installed updates that I didn't seem to able to do anything with! Some of them weren't even for SIMS and that was the only package the school used, not FMS or anything...

 

Needless to say, I uninstalled it from the server and workstations, ran the a SOLUS2 update, walked out to the 2 (yes 2) workstations and upgrading them in a couple of minutes each!

 

After that experience I haven't been in a rush to push SOLUS3 here...

Edited December 1, 2014 by Koldov

[JPatch]

It tends to work properly now!

 

At least now it updates a machine that was off when you ran the upgrade unlike before! The machines off? Oh well, no update for that then!

 

I'e rolled it out to quite a few schools now and, touch wood, all seems to be working! Although might change my tune after the Autumn release

Edited December 1, 2014 by JPatch

[matt40k]

Can't comment of the new UI, haven't used it. The old one, yer, took a bit of understanding, but the idea was sound and once you got your head round it was fine, assuming you've not got DNS issues or rebuilding\renaming workstations every 5 mins. There are lot of benefits of S3 over S2 - central deployment, reporting, automation means you have accurate list of what machines have SIMS installed, that they are all installed the same, on the same version. You'll be suprised how often random machines will pop up when you move the SIMS server and it didn't get it's local connect.ini updated. Least with S3 that gets resolved once and for all. Ain't on S3, you don't get SIMS\FMS\Discover\whatever.

 

Regarding a network of 2 (or even 1), yer, utter pointless-ness, complete overkill. That said, really you shouldn't have only 1 or 2 workstations accessing your MIS. You want more access so data can be entered closer to the source, that said, nursery level that might be an exception to the rule

[vikpaw]

I think the link to installables on SupportNet has been removed, else you could have downloaded it. Perhaps try searching for the Spring release notification, that was historically the one that came as installable, though i think this time even that wasn't, and an installable came out later.