i don't remember exactly what the glitch was... the stock intel driver did not support VESA... or something stupid like that.
--- found it ----
Intel Graphics have been a problem for a long time, the default vesa driver used by Windows & Bart works on most ATI & NVidia Graphics but not most Intel integrated Graphics. http://www.911cd.net/forums//index.php? … p;p=106178
-- --
i even remembered correctly
Only intel on board (and now on processor) video cards are afflicted. (all other video cards are compatible with the generic windows graphic driver)
If you can do mass storage you can do any other pack we have, no problem. it is a simple matter of tagging the onboard intel drivers in the graphics pack INI file. (similar to the mass storage tags). Base will build the plugin if the tags exist in the packs INI file. I can do it if i get a free evening. it's just a INI file edit, the hard part is knowing which intel folders are for embeded graphics.
Base has always ignored txtsetup.oem files with great prejudice.
Perhaps we can address what are our best options to incorporate registry entries.
The INI file would be my first choice.
I DON'T want to parse .OEM files, from my experience parsing INF files that is NOT the way to go. the program i wrote to pull the hwid's and the driver names for the download pages took tons and tons of testing, it seems that INF file writers are sloppy and windows is seemingly tolerant. there are LOTS of exceptions to "rules".
Ultimate Boot CD "UBCD" is a different project than Ultimate Boot CD For Windows "UBCD4Win"
I would like to note that you can include UBCD in your UBCD4Win bootmenu. (nice)