dandirk

Absent Member.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2010-07-12
18:58
1182 views
c:\ opens before app...
This is a weird one...
I am virtualizing a diabetes application called OneTouch...
Had some issues with it even starting but solved those...
Now the C: drive opens when I launch the app, then the app opens. Anyone run into anything like this?
I am virtualizing a diabetes application called OneTouch...
Had some issues with it even starting but solved those...
Now the C: drive opens when I launch the app, then the app opens. Anyone run into anything like this?
3 Replies
dholmesscsd

Absent Member.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2010-07-12
21:13
Haven't seen anything like that. Errant shortcut or command line argument maybe?
Anonymous_User

Absent Member.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2010-07-13
08:33
dandirk wrote:
> This is a weird one...
>
> I am virtualizing a diabetes application called OneTouch...
>
> Had some issues with it even starting but solved those...
>
> Now the C: drive opens when I launch the app, then the app opens.
> Anyone run into anything like this?
>
>
It immediately makes me think of needing something enclosed in quotes,
perhaps a path that contains a space or similar.
> This is a weird one...
>
> I am virtualizing a diabetes application called OneTouch...
>
> Had some issues with it even starting but solved those...
>
> Now the C: drive opens when I launch the app, then the app opens.
> Anyone run into anything like this?
>
>
It immediately makes me think of needing something enclosed in quotes,
perhaps a path that contains a space or similar.
dandirk

Absent Member.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2010-07-13
17:33
I tried to add "" to the startup file, no go same issue. I tried merging all files/reg with same results. Tried to change isolation a few other items with out decent results.
Also changes run from dir settings with no joy, and virtually all settings options...
I believe the main app exe runs through a bunch of checks when started and somehow a path or something is missed and it calls something funny which opens the c:\ drive. Tried to look through a process monitor but nothing really stood out.
I think I will just run a script to kill the window 1 sec after start... thank goodness its easy enough in ZCM... Everything else works fine.
Just anecdotal... Keep en eye out in the registry for uninstall strings and install GUIDS. I haven't narrowed down the exact keys yet but this app kicks off msi auto repair of another completely unrelated app when its run. With 100s of apps though it would be impossible to test against everything, I was just lucky and tested with that particular app...
I removed a bunch of reg keys which seemed to remedy the issue, no need for those keys anyways as a virt app:) Selective isolution also could help.
Ran into something similar with office install, where one of my firt virt apps, would kick off an office repair when ran.
Also changes run from dir settings with no joy, and virtually all settings options...
I believe the main app exe runs through a bunch of checks when started and somehow a path or something is missed and it calls something funny which opens the c:\ drive. Tried to look through a process monitor but nothing really stood out.
I think I will just run a script to kill the window 1 sec after start... thank goodness its easy enough in ZCM... Everything else works fine.
Just anecdotal... Keep en eye out in the registry for uninstall strings and install GUIDS. I haven't narrowed down the exact keys yet but this app kicks off msi auto repair of another completely unrelated app when its run. With 100s of apps though it would be impossible to test against everything, I was just lucky and tested with that particular app...
I removed a bunch of reg keys which seemed to remedy the issue, no need for those keys anyways as a virt app:) Selective isolution also could help.
Ran into something similar with office install, where one of my firt virt apps, would kick off an office repair when ran.