In reply to:

---

Ah, I take it that means you've got two separate copies working for two separate empegs? That's cool, I was trying to remember what other birds I was killing with the stone of the Winsock calls.

---

Yep, works a treat :-)

In reply to:

---

It sounds like changing the tooltip might be do-able, so that's on my to-do list now. Thanks for the suggestion.

---

Ta.

In reply to:

---

It must be a malfuction in that version of PaintShop, because I just got a perfectly good screen shot, including transparency and everything. The resulting screen shot is attached to this post.

Of course, I didn't use PaintShop's "screen capture" feature to do it. Didn't you know that screen captures are built into the Windows OS? The PrintScreen key captures the whole screen to the clipboard (then you select EDIT-PASTE in PaintShop), and Alt+PrintScreen captures the currently selected window. Both methods worked for me just now when I tried them.

---

Forgot all about that. psp allows more control, but I'll try print screen later.

Thanks again.

Tony,
I works like a charm.
Thanks

Hm, does EmpegFace show the visuals? Or do I need the VNC thing for that? And... hm... the sound still comes out of the empeg, I'm assuming, with both EmpegFace and VNC. Well, that's cool, at least I won't have to go over to the stereo to change songs (but since I've been listening to MP3 at home exclusively, I haven't had to go to the stereo in a LONG time).

I'm guessing you didn't try it? Yeah, it displays the visuals & plays from the line (or sled's line) outputs. For streaming you'd need Charcoalgrey's web interface (there may be other ways to stream, but that's the one I know).

-Zeke

For streaming you'd need Charcoalgrey's web interface (there may be other ways to stream, but that's the one I know).

Actually, CharcoalGray's web interface merely puts a pretty face Hijack's built-in streaming feature. To stream from the empeg directly from Hijack, the following URL is used:

http://empeg/?fid=101&ext=.html

(Where "empeg" is the IP address or DNS name of your empeg)

And again, the pebble remains in the hand of the master!

-Zeke

I find
http://empeg?playlists
is easier to remember.

Again, "empeg" being the IP address or DNS name of your empeg

Hey, no fair. He must have added that in a later version of Hijack...

In reply to:

---

My day job involves writing InstallShield programs, so I know all about how to do that.

---

Since my next job will probably involve a lot of installshield scripting could you point me to some handy online resources ?

Since my next job will probably involve a lot of installshield scripting could you point me to some handy online resources ?

InstallShield's own KnowledgeBase: http://support.installshield.com/kb/
Lots of cool scripts and info here: http://www.installsite.org/

A basic understanding of the way IS works is needed to get the most out of these sites. The best thing to do is mess around with the development environment, hack up some scripts yourself, and see what happens. Once you're comfortable with that, you can start messing with the stuff at installsite.

For me, the single most important tool I've ever used in relation to InstallShield has actually been Powerquest's Drive Image product. Here's how I use it:

I have my main development computer, and a test computer. The test computer is strictly for testing my installs. The test computer has two disk drives, C: and D:. Drive D: contains the DriveImage program and a bunch of images. The images are things like:

- Windows 95 clean installation.
- Windows 98 retail clean installation.
- Windows 98 SE clean installation.
- Windows 98 SE with IE 6 installed.
- Windows NT 4 clean installation.
- Windows NT 4 with Internet Information Server installed.
(etc...)

Drive C is the boot drive. Whenever I create an image like the ones above, I make sure it's dual-boot to DOS. So I can boot the system, drop to DOS, go to D:, run DriveImage, and put another image onto the C: drive. Reboot, and it's a clean fresh install of that version of the OS.

I can run my installer against that version of the OS and see if it really included everything that it needed to include, and did everything it needed to do. Far too often, an installer doesn't include enough DLL files and such, and therefore fails on some in-the-field systems. Testing against a pure version of the OS goes a long way towards making sure your installer really works.

This system also allows for very fast testing across multiple platforms. The image restore only takes a couple of minutes, then boom, you're testing in the next OS on your list. Very slick.

A good set of vmware virtual machine images works perfect for something like that too.

We're actually running into trouble with VMware and networking. Issues with the virtual TCP connections and stuff. There are certain test cases that I can't do on VMware machines because of it.

But if you can't spare a second computer, then yeah, VMware is the way to go. Of course, my test box is just an old 100mhz job that's about 8 years old and it still serves its purpose...

Works a treat!

Thanks Tony,

Cas.